Skip to content

P6.2-B: keep monitoring association stable and consume safe static report projection - #219

Merged
masarray merged 23 commits into
mainfrom
fix/p6-2-b-stability-projection
Aug 19, 2026
Merged

P6.2-B: keep monitoring association stable and consume safe static report projection#219
masarray merged 23 commits into
mainfrom
fix/p6-2-b-stability-projection

Conversation

@masarray

Copy link
Copy Markdown
Owner

P6.2-B field stability integration

This draft integrates ARIEC61850 PR #89 after physical SIPROTEC evidence showed two distinct regressions:

  • one-member NamedVariableList probation succeeds, but subsequent automatic full dynamic DataSet activation can abort the production MMS association;
  • static RCBs activate, but field-observed MX FCD payloads can arrive as structured two-process-value + q/t values and must be projected to exact IEC leaves before becoming process-authoritative.

Integration behavior

  • pin the exact reviewed ARIEC PR Add fast and self-healing fault-record workflow #89 engine commit;
  • automatic full dynamic DataSet activation is quarantined in the engine, so ARSAS receives static-report plans plus bounded MMS polling residual instead of scheduling a risky production dynamic mutation;
  • P6.1 static-failure isolation remains unchanged: static activation failure does not trigger a dynamic write;
  • field-observed MX structures project into explicit instMag.f / mag.f or instCVal.mag.f / cVal.mag.f leaves with decoded q/t;
  • ambiguous structured report values remain fail-closed and MMS verification/fallback remains authoritative;
  • no quality value is forced to Good.

Regression coverage

  • exact engine provenance / PR history;
  • field MX projection through the ARSAS consumer safety boundary;
  • ambiguous Boolean structure cannot overwrite scalar process state;
  • P6.1 static failure isolation remains intact.

Do not merge until ARIEC PR #89 and all ARSAS CI workflows are green. Physical SIPROTEC retest is still required before release.

Copy link
Copy Markdown
Owner Author

P6.2-B CI evidence — ARSAS head 3844d45b141c401e524b4ea1c4c75e8b7b7014ab, pinned ARIEC head 249fb130e0e18e7a98e07e8894f24610bdb5642e / PR #89:

  • Build ARSAS run #1293 (32211366441) — SUCCESS
    • immutable engine checkout — success
    • source/release invariants — success
    • restore/build — success
    • full ARSAS regression tests — success
    • portable publish + smoke test — success
  • Validate Windows installer run #279 (32211366443) — SUCCESS
    • restore/build/test — success
    • installer compile — success
    • silent install/uninstall smoke — success
  • Validate IO List Testing run #279 (32211366483) — SUCCESS
  • Validate SV evidence bundles run #415 (32211366451) — SUCCESS

Keep draft/unmerged pending physical SIPROTEC retest. Acceptance focus: first healthy association must stay alive, static RCB must start without a preceding full dynamic mutation, supported MX report structures must project to the exact selected leaf with real q/t, and ambiguous report structures must remain MMS-authoritative rather than being guessed.

@masarray
masarray marked this pull request as ready for review August 19, 2026 09:18
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@masarray
masarray merged commit 45d4bbd into main Aug 19, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant