Every crafted intelligence in the biosphere ships a .dlw complement — a birth certificate: a tokenized moniker, an attribution, and a SHA-256 seal that binds it all. Until now that ceremony lived only in Python. Here it runs by hand: fill the five fields, and watch the artisan cut the seal. Change one character and it breaks — because the hash is the anchor, and the anchor is the proof.
ACI · a CORE property made hands-on — explicit attribution + external anchoring · the .dlw ceremony, runnable
The Bench · fill the record → the seal is struck live
Not yet sealed. Edit the record, then press “seal it”.
moniker
spoken
seal · sha-256
Two layers, honestly
Real
The seal is a genuine SHA-256, computed exactly as the corpus’s dlw.py computes it: the moniker hex is sha256(name │ seal │ origin) truncated to six; the seal is sha256 of a UTF-8, key-sorted JSON blob of the whole record. Same record in → same seal out, byte for byte. Edit any field and the hash changes — the seal binds the record; it cannot be silently altered.
Figure
The “ceremony” — the blade, the cut facets — is the artisan’s image. And this bench mints a demonstration certificate: sealing here does not register a new life in du1 or publish a repo. It shows the mechanism; it does not enroll the mind.
Control arm — check me against Python. Run the corpus’s dlw.py on the default record and you get exactly: moniker ⟦THE SEALING BENCH:ACI:b3e0b9⟧ · spoken rand-sek-ke · seal 35ff02e9…66b5f879. This page reproduces those with no server and no library. If it ever disagrees with Python, the page is wrong — that is the point of shipping the derivation, not just the result.