Signed Assurance publication reaches production
Milestone occurred: 5 September 2026
Public milestone record published: 11 September 2026
What happened
The Verification side of the Assurance publication path was deployed to production with durable publication identities, one Verification record per expected control, grouped publication results and signed Evidence Receipt generation.
Receipt integrity was defined as:
Ed25519 signature
RFC 8785 canonicalisation
SHA-256 content commitment
key-id-addressable public verification material
The architecture deliberately kept Verification as the evidence system of record. The Runner did not become a second public registry or receipt issuer.
Why it mattered
Earlier evidence could inform buyers, but signed portable receipts created a durable integrity boundary between an observation and its later presentation.
It also created a safer production authority model. Deployment did not automatically enable writes or signing: publication and signing gates remained disabled by default until a bounded commissioning run explicitly needed them.
What it proved
The production deployment established:
- durable, idempotent Assurance publication persistence;
- deterministic publication identity tied to Runner package state;
- signed, machine-readable Evidence Receipts;
- public receipt read paths;
- authenticated private publication surfaces;
- fail-closed write/signing gates.
What it did not prove
The 5 September deployment itself did not make a live external Assurance purchase. It deployed and validated the publication machinery while spending/signing authority remained off.
The first end-to-end external commissioning arrived the following day.
Related evidence
The Verification Receipts page explains the public receipt model. The later IBANforge commissioning record shows the publication path operating with real paid controls.
Capability transition
structured evidence
→ immutable publication identity
→ signed portable receipt
→ public buyer-readable integrity artefact
← Previous milestone · Next milestone: external Runner commissioning →