Writing index
Development sequence
July 15, 2025
8 min read

Verification Infrastructure Development Sequence

The development sequence moves from a reference implementation to cross-implementation evidence and then to production integration. Each phase has a different technical objective. External verification artifacts provide the primary measure of progress. Adoption claims provide secondary context.

01 · Sequence

Three phases, three exit tests

2025

Reference implementation

Objective. Establish a complete path from policy artifact to mediated runtime decision, certificate record, and replay bundle.

Evidence. Public schemas, reference verifiers, conformance traces, runtime measurements, and reproducible incident records.

Exit test. Independent teams reproduce selected verdicts from exported artifacts and identify implementation disagreements through the conformance suite.

2026

Cross-implementation interoperability

Objective. Move from one reference stack to multiple implementations that share certificate semantics, replay profiles, and permission-state conventions.

Evidence. Cross-runtime certificate verification, replay comparison, version-transition tests, and third-party evaluation reports.

Exit test. Evidence produced by one implementation is accepted by an independent verifier built from the public specification and reference material.

2027

Deployment integration

Objective. Place verification gates inside production deployment and execution workflows for consequential autonomous actions.

Evidence. Production conformance records, incident reconstruction data, policy-version histories, and public interface specifications.

Exit test. Operational teams treat policy identity and verification evidence as standard deployment artifacts across supported environments.

02 · Phase one

Reference implementation

The first phase establishes semantic closure across the stack. Source policy, compiled monitor, runtime verdict, evidence record, and replay result need a shared identity model. The main engineering risk is a gap between the declared semantics and the deployed decision path.

Public conformance traces serve as the central artifact. Each trace states the expected decision under the reference semantics. The deployed runtime records its own decision and evidence bundle. Disagreement produces a test case for implementation correction.

03 · Phase two

Cross-implementation interoperability

The second phase tests whether evidence preserves meaning across independently built systems. Shared schemas are necessary, though schema compatibility alone is insufficient. Certificate fields need common interpretation. Replay profiles need comparable semantics. Version transitions need explicit rules.

Interoperability events focus on verifier agreement and replay reconstruction across implementations. Results are published as compatibility records with identified semantic differences instead of aggregate scores that hide disagreement.

04 · Phase three

Production integration

The third phase moves verification records into ordinary deployment practice. Policy identity forms part of release metadata. Runtime verdicts form part of effect records. Replay artifacts join incident handling. Version transitions join change control.

This phase is complete once external evaluation stays feasible under production constraints. Performance optimization preserves evidence identity and semantic traceability.

05 · Programme metrics

Measure evidence quality directly

MeasureInterpretation
Verifier agreementIndependent implementations reach the same result from the same declared artifacts.
Replay consistencySelected traces reconstruct the production decision under the declared profile.
Policy coverageConsequential effects pass through a governed decision path with named policy identity.
Version traceabilityEvidence records preserve the policy and runtime identities associated with each decision.