Skip to content

M2.14 SG: show model-verified active setting values in parameter rows - #569

Draft
masarray wants to merge 3 commits into
feat/ied-browser-m214-control-state-evidence-20261015from
feat/ied-browser-m214-sg-value-projection-20261015
Draft

masarray wants to merge 3 commits into
feat/ied-browser-m214-control-state-evidence-20261015from
feat/ied-browser-m214-sg-value-projection-20261015

Conversation

@masarray

Copy link
Copy Markdown
Owner

M2.14 — fix real SG parameter values, not a cosmetic placeholder

Stack #560 → #563 (Thread A) → #567 (A/B validated) → #568 (read-only SGCB/GoCB validated) → this PR. Owns Browser presentation and explicit SG read plan only.

Root cause

The SGCB detail pane grouped all SG + SE leaves into a synthetic DO root and set its ValueReference only for a single-attribute DO. On a real relay with multiple SG/SE attribute declarations this results in an unbound Not read root even when exact SG leaf observations exist. It also reads SE edit-group fields unnecessarily when choosing active SG inspection.

Fix

  • Project exact active FC=SG parameter branches directly via the existing lazy, schema-constrained AttributeRows projector, e.g. ATCC1.BndWid.setMag [SG] linked to ...$SG$BndWid$setMag$f, and f [SG] on expansion.
  • Preserve canonical source/FC, unit provenance, lazy descendants, and association fences; do not infer active group from SE, change group, reserve, or write.
  • Prefer unique verified primitive f if both a structured parent and its primitive are in the declaration.
  • Explicit selected SGCB Read targets active SG plus inventory-proven read-only SGCB status; no SE edit-group sweep. Global Read All semantics are unchanged.
  • Four negative/positive regression tests and updated presentation baseline; no engine pin, Report/GI/cyclic MMS, SSOT, or stable branch changes.

Acceptance

Require exact-SHA Windows compile, full ARSAS regression, pinned engine/native CTest, artifact verification. A screenshot from a physically connected ZIV AVR is still required to prove what SG attributes the device actually permits read-only access to. Other CF unit issues will be handled under Thread A's authority rather than a competing unit decoder.

This branch has not been deployed

No deployments
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