Satoshium Anchor · Publication

Publication Principle

Publication Gate

Anchor should use a formal Publication Gate before a draft Integrity Reference becomes publicly authoritative.

Public Authority Boundary

Publication makes Anchor authoritative for the published Integrity Reference, its Version, its integrity metadata, its provenance, and its relationships.

Publication does not make Anchor authoritative for the Source Artifact's substantive meaning.

Publication Preconditions

Before Publication Gate approval, a production Integrity Reference should have:

Validation architecture should eventually convert these expectations into explicit institutional checks.

Publication Gate Decision

The Publication Gate should produce a simple institutional decision:

The Publication Gate is not a Verification Result and not a Lifecycle State.

Publication Gate Approval

APPROVED means Anchor has determined that the Integrity Reference is ready to enter public institutional use under its current Anchor Version.

Approval does not mean:

Publication Gate Rejection

NOT APPROVED means the record is not yet eligible to become publicly authoritative under Anchor.

Potential reasons include:

Rejection should preserve the draft workflow without creating a misleading production publication event.

Publication Timestamp

Every publicly authoritative Anchor Version should preserve:

The timestamp should represent the moment the Version entered public Anchor authority, not necessarily the time the Source Artifact was created or the integrity material was generated.

Time Separation

These timestamps answer different institutional questions and should remain separate.

Canonical Human Representation

The canonical HTML page should communicate the same institutional facts expressed by the canonical machine-readable record.

Human presentation may reorganize information for clarity, but it must not contradict the canonical JSON.

Canonical Machine Representation

Canonical JSON should preserve the structured form of the Integrity Reference under the governing Schema Version.

It should be suitable for:

Human / Machine Consistency

Both should represent the same:

Canonical vs. Derived Representations

Anchor may produce derived pages, indexes, summaries, mirrors, or discovery surfaces that are not canonical Integrity Reference representations.

Derived surfaces should point back to the canonical Anchor record.

Canonical URL

Publication should eventually assign stable canonical locations for the current Integrity Reference and its machine-readable representation.

Exact URL syntax remains unfrozen until the Anchor Identifier syntax is finalized.

Current Version

A stable Anchor Identifier should resolve to the current canonical production Version.

Historical Versions should remain directly accessible through explicit Version history.

Historical Version Publication

Public presentation should make clear which Version is current without suppressing previous states.

Correction Publication

Anchor should not create the false appearance that the corrected value was always the original published value.

Lifecycle Publication Behavior

Draft records should not appear as publicly authoritative production records.

Withdrawal Does Not Mean Deletion

A withdrawn Integrity Reference should remain historically resolvable unless a separate legal or security requirement prevents public access.

Publication State

Publication architecture now proves the need for a small Publication State vocabulary.

These remain intentionally unfrozen until Validation and Procedures determine whether `approved` belongs as a state or should remain exclusively a Gate decision.

Gate Decision vs. Publication State

This distinction keeps approval workflow separate from the state carried by the Integrity Reference.

Publication and Verification

Later Reverification does not necessarily require republication unless canonical record data changes.

Publication and Validation

The Validation page should formalize the exact sequence and PASS/FAIL behavior.

Publication and Versioning

Version N remains historically preserved.

Publication and Maintenance

Publication Record

Whether Publication receives its own permanent identifier remains unfrozen.

Publication Procedure

Publication Principle

Publication should convert a completed Integrity Reference into a durable public Anchor record only after its structure, evidence, and canonical representations are ready for independent review.