Engineering Record

The changelog, kept honestly.

A protocol whose transparency log is append-only should keep its own history the same way. Every phase is recorded — what shipped, what is gated, and what comes next — never silently rewritten.

Phase 2 complete — the verifiable core Phase 0.3 · 2026-07

The TypeScript SDK reaches feature-complete for the trust core: canonical encoding, scope grammar, CPoA reliance, settlement pre-checks, and the transparency log — all implemented, strictly typed, and tested.

  • 36 tests pass on Node 22, including exhaustive Merkle verification to tree size 33 and both split-view and forged-entry detection.
  • Zero runtime dependencies — base58check, canonical JSON, and Merkle machinery implemented from first principles.
  • The reliance rule lands as a single choke point, assertReliable(), called by settlement rather than reimplemented.
  • Public interactive verifier ships — real WebCrypto SHA-256 over the document bytes, live on the Verify page.
The standards track opens Standards 0.2 · 2026-05

TAP-1 through TAP-8 are published as real draft specifications — status ladders, dependency graphs, and open-issue registers — legible to a working group on day one.

  • Eight TAP drafts with the design invariant enforced by the PR template: no standard may make reputation authoritative.
  • Governance framework published: three councils, seat exclusivity, and auto-sunsetting emergency powers.
  • SmartPy contract sources for the registry and CPoA ledger added as pre-compilation, audit-gated drafts.
Genesis — the argument in software Phase 0.1 · 2026-04

The repository is seeded as an argument rendered in code: trust as a function of authorization, not popularity. Structure places the most consequential content shallowest — standards and governance at the top level.

  • Cryptographic Power of Attorney framework formalized and submitted to NIST NCCoE as a public comment.
  • The five commitments established and wired to enforcement points: default deny, fail closed, no hidden clocks, attestation over reputation, one choke point per rule.
  • Dual-license structure staged (Apache-2.0 for code, CC-BY-4.0 for specs), each self-identifying as counsel-gated.
Phase 3 — the privacy extension Planned Next · TAP-9/10

Planned. Transparent STARK proofs (Cairo/Stwo) wrap the attestation and payment layers in confidentiality with structured accountability — privacy that hides the values, never the validity.

  • Scope-compliance and revocation-freshness circuits ship before confidential settlement — confidentiality without them is dangerous.
  • A five-tier disclosure model: public, counterparty, institution, examiner, court.
  • Every circuit treated as an SR 11-7 model from day one — conceptual soundness, challenge review, outcomes analysis.