∞ unwindcode
Transmission 031
Publication Governance

Ready is not live truth

A green build can still be the wrong public body. The Brain must prove identity before it mutates production.

The Active Source-of-Truth Gate01 / 08
∞ unwindcode
Why it matters

The site has to know which body the world sees.

Local source, deployed artifact, active alias, archive, metadata, and public APIs can drift apart. Publication begins by proving they describe the same organism.

Publication is identity transfer02 / 08
∞ unwindcode
Five proofs

The gate checks five truth surfaces.

Live laneWhich deployment receives the active domain?
Local sourceDoes the worktree contain every public route already live?
DiscoveryDo homepage, archive, sitemap, LLMS, and AI services agree?
Public APIsDo status, search, grounding, transmissions, and assets prove the same state?
Internal boundaryAre carousel packets still creator-only?
Approval lockDoes mutation wait for the creator?
No source without boundary03 / 08
∞ unwindcode
Gate protocol

Inspect. Compare. Verify. Classify. Ask.

01
Inspect active domainFetch what readers and agents actually see.
02
Compare local sourceConfirm local contains every public live route.
03
Verify contractsCheck discovery files, data JSON, and public API state.
04
Ask before mutationDeploy, alias, and posting authority stay human-gated.
The hand does not move until the gate passes04 / 08
∞ unwindcode
Threat model

Most publication failures are identity failures.

Stale laneThe domain serves an older deployment.
Live-ahead driftProduction has routes missing locally.
Discovery splitPage, sitemap, LLMS, and archive disagree.
API splitStatus or retrieval contracts cannot prove the page.
Social packet leakInternal posting assets become public CTAs.
Green build illusionTests pass, but nobody verified the active body.
Stale truth is still drift05 / 08
∞ unwindcode
Next cell

Build the Release Identity Controller.

01Proof packetLatest route, live route, lane, counts, APIs.
02Failure labelsStale lane, live-ahead, missing data, API split.
03Hold stateStop deploy and alias commands until reconciled.
04Memory writePassed gates and failed gates become proof memory.

The cell does not publish. It tells the operator whether publication is allowed to be considered.

Proof before production mutation06 / 08
∞ unwindcode
Approval boundary
Proof opens clarity.It does not open deployment authority.
The creator still publishes.Deploying, aliasing, posting, syncing, spending, signing, and mutation remain gated.

The Brain may prepare the release package. The human decides whether the public body changes.

Approval before deploy07 / 08
∞ unwindcode
Next-cell memory
Transmission 31

Know which body you are writing into before you write.

A living website does not just publish. It remembers which public body is active, proves the body is current, and waits for approval before changing it.

Read the guide on UnwindCode.ai08 / 08