Validation Evidence Graph Runtime Engine Follow-Up #171

Scope rescope — 2026-09-20

Consume independent current_execution and optional chronology without inflating test results into full requirement coverage. The full validation graph is not a prerequisite for #481 or ordinary current-run validation.

R09 boundary alignment: nold-ai/specfact-cli#740 and #481; this issue retains its existing schema or runtime ownership. This section supersedes conflicting default-workflow and dependency statements below; other acceptance criteria remain in force.

Synchronized scope (2026-06-07)

Modules-side runtime follow-up for the validation evidence graph engine paired with nold-ai/specfact-cli#241.

This owns bundle-side validation engine execution, grouped command wiring, runtime checks, and evidence output integration. It must not implement upstream requirements-to-code lifecycle orchestration.

Status note: modules repositioning is merged to dev, not main; keep open until the active runtime implementation is complete.

Normative acceptance and delivery order — 2026-09-20

Current execution is independent from optional chronology. Passing current tests do not establish historical failing-before proof, complete graph coverage or protected CI authority. Missing mappings remain unassessed or explicit findings; original producer outcomes/references remain independent. Fresh current-only verification needs no prior receipt, full-chain run or duplicate proof execution.

Core #247 owns the envelope contract and precedes core #241 and modules #169. Modules #171 consumes core #241 plus modules #169. The stale core #241 prerequisite on #247 is removed; existing unrelated prerequisites remain. Only actual full-chain emission requires full-chain results. R09 and workflow delivery do not become downstream blockers of this broader feature.

The normative OpenSpec deltas preserve these rules during archival. Serialization uses distinct additive requirements without replacing producer-owned validation or policy requirements. Core remains contract-only; modules owns emitters/file persistence. All implementation tasks remain unchecked.