[masarray]

P0-A — generic IEC 61850 IED identity correctness (code trial, NOT field acceptance)

Engine masarray/ARIEC61850 PR #177, exact HEAD ccf31f60095ea65f9095514f0fa0102060962049; engine CI run #39228439974 SUCCESS.
Consumer layered on draft ARSAS PR #621, exact source 5c9f2732f9ce68290c2fb7d16f221e382a68eac9. Engine lock unchanged historical ancestry with explicit P0-A trial descriptor.

Behavior

• Preserve canonical SIEBCU from five observed MMS domains; no destructive known-suffix stripping.
• All domain-only and operator-supplied names remain provisional, never falsely promoted to wire-exact.
• Verified IID/SCL promotion requires pinned, unchanged source SHA-256, uniquely matching IED/AP/full case-sensitive LD domain set, exact endpoint IP and selected AP. Reject missing/stale/wrong IP/AP/SCL topology.
• Consumer passes selected AP through both opened IID and SHA-bound remembered endpoint resolution; reuses canonical runtime identity projection.
• No vendor-specific branches, second MMS engine, discovery writes, controls, RCB mutations or cyclic scans.

Regression/CI

R7 exact-SHA Windows workflow SUCCESS: https://github.com/masarray/arsas/actions/runs/39233599772

• Engine C# regression 1152/1152 PASS
• ARSAS C# regression 2368/2368 PASS
• Other policy checks currently green: provenance, golden budgets, repeat-run, interoperability reference, SCL/R7, mainline readiness, SV/IO validation, merge and production promotion policies.
• Earlier 5 failing history assertions were corrected by separating immutable M2.17-K/physical ancestry from current P0-A trial, not deleting tests or permitting field promotion.

Remaining gate

Windows Build ARSAS portable/installer workflows are running at time of writing. Physical IED testing is unavailable and NOT CLAIMED. Keep PR draft, no merge or physical acceptance from CI alone. Next slice P0-B targeted, resumable RCB planner.