Skip to content

discovery: preserve exact primary type semantics in live SCL - #138

Closed
masarray wants to merge 5 commits into
mainfrom
fix/exact-primary-type-semantic-parity
Closed

masarray wants to merge 5 commits into
mainfrom
fix/exact-primary-type-semantic-parity

Conversation

@masarray

Copy link
Copy Markdown
Owner

Goal

Make live-discovery SCL semantics follow exact MMS TypeSpecification evidence instead of allowing a generic CDC fallback to overwrite a proven primitive type.

Changes

  • refine only low/medium-confidence generic SPS inference when an exact stVal primitive is available;
  • exact integer stVal refines generic SPS to INS;
  • exact Boolean stVal confirms SPS;
  • SCL export preserves an exact MMS primitive bType instead of replacing it from a lower-authority CDC fallback;
  • add regression coverage proving a generic status object with exact INT32 stVal exports as INS / INT32.

Safety

  • no object-name based integer classification;
  • no vendor-specific rule;
  • standard/high-confidence CDC mappings keep precedence;
  • unknown or non-exact type evidence remains unchanged;
  • no MMS wire/discovery request changes.

This remains a draft candidate until application integration and physical field verification prove semantic and runtime parity.

masarray commented Oct 7, 2026

Copy link
Copy Markdown
Owner Author

Coordination note for parallel work: #145/#144 is reusing the same authority principle established here—exact MMS TypeSpecification outranks generic inference—but only for RCB mutation safety. This PR's discovery/SCL semantic-refinement scope is being left untouched; no duplicate CDC/export implementation is being added in #145.

masarray added a commit that referenced this pull request Oct 22, 2026
…CL semantics #138

Consolidate exact #130 12 new SV analysis/docs/tests blobs and #138 four proven non-overlapping discovery/SCL source and test blobs; Iec61850StandardModelRegistry.cs already byte-identical to #138. Explicit parents preserve source ancestry. No updates to main or ARSAS engine lock, no release/FAT qualification. Validate exact merged candidate via Windows CI.

Copy link
Copy Markdown
Owner Author

Cleanup of verified stacked Git ancestry on 2026-10-22: original source SHA 5d8c9959f638290a7aaf45988ef45ed823639d2a is fully contained (0 missing commits) in canonical consolidated draft #190, currently 14b19d30466fd296ad1e6d0bddcdd574992bc464; exact merged-tree Windows CI #39778971482 passed 1,262/1,262 tests with no build warning/error.

Closing this now as consolidated/superseded, NOT merged to main; no branch deletion, no source history loss, no ARSAS repin, no mainline engine source promotion. Original physical validation and follow-ups still apply, and #190 remains draft. If #190 is discarded, this PR is available to reopen.

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