SERVICE + LEDGER STATUS
The current truth.
- LEDGER WRITE STATE
- CLOSED
- RECORDED ENTRIES
- 0
- WITHDRAWN PLACES
- 0
OWNERSHIP: COMMITTED · LEGAL MEMBERSHIP: NOT YET ISSUED. A Founding Ledger entry is not a share, security, token or legal membership. Withdrawn places keep their ordinal forever as tombstones; numbers are never reassigned.
ENVIRONMENT WRITE GATE: ABSENT · DATABASE MODE: CLOSED · BOTH MUST AGREE BEFORE ANY ENTRY CAN SEAL.
MEMBERSHIP ISSUANCE · LIVE
What is not yet true about us.
The Founding Ledger stays closed until every one of these is evidenced. When one slips, this page says so before anyone asks.
- GATES MET
- 0 OF 16
- OLDEST OPEN GATE
- Legal status and privacy notice reviewed
- BLOCKED BY
- a named legal reviewer (handoff decision 12)
- SLIPPED
- 0
- 01Legal status and privacy notice reviewedA licensed reviewer has signed off on the entry copy and the privacy notice.BLOCKED BY: a named legal reviewer (handoff decision 12)OPEN
- 02Public/private data map approvedDATA-MAP.md is complete and approved by the legal controller.BLOCKED BY: a named legal controller (handoff decision 2)OPEN
- 03Identity and recovery path testedA person can lose access and recover it without a steward reading their mail.OPEN
- 04Atomic entry and continuation tests passConcurrency and First Continuation tests pass against real PostgreSQL.OPEN
- 05Idempotency and abuse controls passIdempotent replay and per-actor rate limits verified.OPEN
- 06Correction, withdrawal and export workA person can export, correct and withdraw without asking anyone.OPEN
- 07Encrypted backup exists and clean restore rehearsal passesA restore FROM THE REAL BACKUP into a clean environment, with the digest chain recomputed.BLOCKED BY: an off-site backup target (handoff decision 8)OPEN
- 08Incident owner and support path are namedA named human answers, with a named escalation path.BLOCKED BY: founder-steward (handoff decision 7)OPEN
- 09No interface claims legal membershipEvery entry and receipt surface carries the legal-status qualifier.OPEN
- 10Pause/rollback path is testedPausing stops seals while reading and data rights keep working.OPEN
- 11Monitoring exposes failures without exposing private dataFailure is visible; no raw email or IP metric is published.OPEN
- 12Email domain, bounce and complaint handling workA verified sending domain with SPF, DKIM and monitored DMARC.BLOCKED BY: domain registration (handoff decision 10)OPEN
- 13Production plan/cost and spend controls are acceptedA plan chosen, a spend limit set, both recorded.BLOCKED BY: founder-steward (handoff decision 9)OPEN
- 14Genesis/origin treatment has a decision receiptHow #000001 exists in production is decided and receipted.BLOCKED BY: founder-steward (handoff decision 3)OPEN
- 15Founder-steward signs and publishes the readiness receiptA published receipt naming every gate above as met.BLOCKED BY: every gate aboveOPEN
- 16Environment and database write gates are deliberately openedALLOW_CANONICAL_WRITES=true and system_state.mode=OPEN, each with a receipt.BLOCKED BY: the readiness receiptOPEN
CONFORMANCE · PUBLISHED EITHER WAY
We publish our own failures.
The invariant suite runs against the real database and appends its result to the canonical log. There is no flag that hides a failing run.
NO CONFORMANCE RUN HAS BEEN RECORDED IN THIS ENVIRONMENT.
ANCHORS
The record outside this database.
NO ANCHOR PUBLISHED YET. AN ARCHIVE STARTED IN YEAR THREE IS A MARKETING ARTIFACT; STARTED IN MONTH ONE IT IS A RECORD.