You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sweep declared manifest outputs against written columns before they become load-bearing #700
Follow-up from the PR #690 review (workstream E of #665; see also #145).
The class
The licensed-data acceptance on #690 caught a declared manifest output (state_pension) that was an SPI concept, not a persisted frame column — dormant for as long as outputs were purely declarative, refused at full rung the moment country_stage_plan compiled outputs into StagePlan.produces. As the review put it: the other manifests may carry the same latent class, dormant until they too become load-bearing. Each discovery via a build costs a credentialed full-rung run; a static sweep costs one pass.
Scope
Validate declared outputs against what the runtimes actually write, statically, for every source manifest not yet load-bearing:
us/source_stages.json (39 stages) against the us_plan stage produces declarations and runtime constants — note the US plan has stages with no manifest entry, so the mapping needs care rather than a naive zip.
be/source_stages.json against its implementations.
PR #690 already pins the two migrated UK stages' outputs to named runtime written-column constants (TestDeclaredOutputsAreWrittenColumns); this issue extends the discipline to the rest.
Acceptance
A conformance test (or one per country package) that fails when a declared output names a column no runtime constant or plan declaration backs; every existing latent entry either fixed or documented with an owner.
Activity
Review response: pin declared outputs to runtime written-column const…
Review response: pin declared outputs to runtime written-column const…