Pre-Phase-20: repair graph identity and establish operational authority

[404khai]

Result

Establishes the approved pre-Phase-20 prerequisite foundation. Published graph identities now bind and verify canonical routing semantics; dispatch owns coherent operational/execution state, checked namespace-scoped identities, atomic in-memory transitions and same-effect recognition. Simulation uses the shared transitions while retaining its driver clock and queue.

A named static-road temporal policy permits delayed insertion, fleet and recovery publication while protecting feasibility, forecast validity and the original Phase 17 selection claim. Versioned records retain evaluated decisions separately from actual committed facts. The signed Q1–Q33 contracts, three cohesive ADRs and existing specifications are reconciled.

All 18 prerequisite gates PASS. Phase 20 is not implemented.

Review

The four commits separate normative contracts, graph repair, operational foundations, and reproducible evidence. Start with the completion report and implemented runtime boundary. Large JSON additions are measured benchmark/replay evidence grouped in the final commit.

Validation

• Formatting, strict workspace/all-target Clippy, locked workspace tests: 218 passed, zero failed.
• Release workspace build and warning-free Rustdoc passed.
• 38 archived Phase 15–19 semantic comparisons and exact current replays passed.
• Independent fleet/recovery oracles, seeded operational invariants and focused graph/execution/publication regressions passed.
• Measured graph lifecycle, 101 boundary samples and 11 scenario replay samples/configuration; raw results, hardware/configuration/hashes and logs retained.

Limits

Temporal certification currently supports static routing and evaluable active prefixes; unsupported proofs fail closed. Authority is volatile and in-memory. No HTTP, credentials, database, broker, distributed services, durable recovery or end-to-end delivery guarantee is introduced. Phase 20 requires separate user confirmation and authorization.

CI portability follow-up

The initial Ubuntu Tests job exposed a fixture assumption: traffic overlays pinned
to macOS-compiled graph bits were used against newly compiled graphs. Published
verified graph/provenance/manifest bundles now accompany those overlays. CLI tests
and commands load these exact bundles, with deep verification and explicit
wrong-snapshot rejection tests. Production digest validation remains unchanged.
The all-feature workspace suite now passes 218 tests locally; strict all-target,
all-feature Clippy and formatting pass. Follow-up logs are retained in the report.