PUBLISH · REGISTRY · APPEND-ONLY · HASH-ONLY · FAIL-CLOSED

Publish minimized proof

Generate a minimized, hash-only registry entry. This does not publish your private release artifact. It produces an append-only entry containing deterministic evidence fields for public matching.

Minimize public surface · publish hash-only evidence
FAIL-CLOSED NOTICE · PUBLIC LEDGER RULES
Append-only means: no edits

If you need to change something, you do not edit old entries. You publish a new entry/event. Missing required evidence ⇒ INVALID.

Publish input

Paste the deterministic evidence produced by the release generator and verification workflow.

Minimized registry entry fields

Keep it minimal. Do not publish sensitive data.
Required. Missing/invalid format ⇒ INVALID.
Required. Must be parseable. Missing ⇒ INVALID.
Status is useful for registry interpretation (still hash-only).
Default registry target (viewer expects):
/registry/registry.json
This page produces a single entry object. Append it manually to the registry list (append-only).
Publish terminal
WARN
required
payload_sha256, timestamp
public
name + hash + timestamp (+ status)
mode
append-only (no edits)
result
WARN

Entry output (copy)

append-only
payload_sha256
timestamp
name

Registry entry JSON

Append this object to your registry list. This is minimized and hash-only.

Append-only discipline

Do not edit past entries. Changes must be new entries or events referencing prior hashes. This prevents silent rewriting and keeps auditability intact.