WITNESS / DELIVERY DIODE
A Git commit records an offer or a receipt; a remote ACK file is checked at append. An OFFER is never counted as delivered. Live revalidation of a remote file is separate from historical ledger verification.
INDEPENDENT WITNESS BINDINGS
A
B
C
GitHub Actions confirms the account ID before accepting an event. B/C remain closed until independently enrolled in the reviewed Git registry. Names are account bindings, not cryptographic personhood proofs or votes.
Memory boundary
PAST → OBSERVES PRESENT → DESERVES FUTURE → RESERVES A :: own lane and actor B :: own lane and actor C :: own lane and actor quorum = null agreement = NOT REQUIRED vote = NONE write = APPEND-ONLY remote action = NONE
DELIVERY HISTORY / OUTBOX AND RECEIPTS
MANUAL ONE-WAY DELIVERY
1. Append a witness observation in Gate 08 using a registered GitHub account.
2. OFFER a temporal event to a destination repository.
3. For 0root, create a receiver ACK file in the Hallway repository. It verifies the OFFER against TOPH first.
4. Find the ACK file's public Git blob SHA in Gate 07; then use the TOPH delivery Action again with RECEIPT, OFFER number, path and SHA.
The TOPH workflow writes only to TOPH. The receiver workflow writes only to its own repository. The bridge is a two-step, proof-bearing exchange—not shared private filesystem access or unattended work.
CORPUS BRIDGE / SOURCES
Hallway receipt inbox contract
Identity and receipt regression tests
The history is public metadata only. Neither local browser memories nor private repositories are exposed through this link. Any receiver outside 0root requires an equivalent public ACK contract and its own authorized writer.