PI6 — AuditSpine, audited (May 2026)

A public, sealed, offline-verifiable record of what AuditSpine did in PI6. No login. No account. No vendor-attested trust. Walk the evidence yourself; verify it offline against the open spec; bring your own criteria for findings. This page is itself sealed and re-verifiable — click Verify this page at the bottom.
🔒 Every closed circle is cryptographically sealed by three independent parties — Customer (SAO) · AuditSpine (COS) · Auditor (VAL). ▸ Verify yourself, offline, with no account.
SEE

The first thirty seconds — what was PI6?

Center = AuditSpine. The four rings = the workstreams PI6 advanced (substrate · circle UI · safety · public-AI). Color is status (orange = at-focus · blue = workstream · green = downstream customer/partner). Drag to rotate the sphere; click any node to read its plain-English summary.
AuditSpine (center) advanced four workstreams in PI6. Click any node above to read the plain-English summary. Drag to look at the substrate from a different angle.
WALK

Walk the PI6 record — by time, by stage, by hierarchy

Three views of the same sealed record. Time axis (May 8 → May 26, 19 days): click a day to read what was active. Stage sequence (the 14-stage AuditSpine delivery pipeline): the canonical lifecycle every initiative passes through. Drill-down (hyperbolic): click any initiative to re-center; drill arbitrarily deep without losing context.
PI6 time axis · 19 days between the two sealed PI-bracket bundles
Click a day-disk above (or either focal PI-bracket seal) to see what was happening on that date.
Stage sequence · the 14-stage AuditSpine delivery pipeline
Click a stage above to read its name. Every initiative threads through this lifecycle.
Drill-down · click any node to re-center · the boundary is infinity
PI7 backlog hierarchy. Click any initiative or epic to re-center on it. The boundary represents infinity in hyperbolic distance — drill arbitrarily deep without losing context.
TRUST

Verification without cryptography expertise

Three levels of trust, each available at every drill-down depth above. None of them ask you to trust AuditSpine — they ask you to trust the math, after you've checked it yourself.
LEVEL 1 · VISUAL
Three independent signatures
Every sealed item carries: SAO (Customer) → COS (AuditSpine) → VAL (Auditor). None of the three parties can change the record without breaking the chain. Each signed independently.
LEVEL 2 · MANUAL CLI
Verify this offline
Download the sealed bundle + the signed Verifier-CLI. Run locally; no network call to AuditSpine. Runs in an air-gapped lab if you prefer. $ auditspine-verify pi6.tar.gz
LEVEL 3 · RE-IMPLEMENT
Write your own verifier from the spec
The Bronze Hash Protocol · SAO/COS/VAL seal protocol · canonical-bytes spec are all open. Python + Go reference implementations proven byte-identical. Trust is structural, not vendor-attested.
JUDGE

Findings — your criteria, against the sealed record

Sealing ≠ auditing. Sealing makes the work inspectable; auditing is the evaluation of evidence against criteria to form findings. The left chart shows PI6 as a dual-arc ellipse: upper arc = the planned measurement trajectory; lower arc = the sealed actuals; vertical gap at any day = divergence. Click a sealed-day point to get its doctrine classification on the right. Bring your own YAML criteria to add custom findings.

Default findings (team's published criteria)

Attribution coverage · loading…
Computed from the sealed PI bundle. Refresh if this doesn't populate.
Engine seal-chain coverage · loading…
Computed from the sealed PI bundle.
Agents active · loading…
Computed from the sealed PI bundle.
PI close hygiene gate
PI6 closed 2026-05-26T08:00Z with the retroflip-audit + carry-decision sweep on record. Zero unresolved retroflip candidates at close.
Click any green sealed-day point on the dual-arc to read its classification: WITHIN SEALED POLICY · ADVERSARIAL NOVELTY · NEGLIGENCE.