Anchor · Procedures

Satoshium Anchor · Production Procedures

Production Procedures translate Anchor's institutional architecture into ordered, executable workflows.

The public Procedures page serves as the institutional landing page. Individual procedures are maintained as governed Markdown artifacts unless future operational need justifies separate public pages.

Procedure Principle

Architecture defines what Anchor means.
Procedures define what Anchor does.

Integrity Reference Production Procedure

Creates a new Integrity Reference from Source identification through Canonical Representation, integrity generation, provenance, relationships, staged Validation, Initial Verification, canonical publication representations, and handoff to Publication.

Defined

Integrity Verification Procedure

Reconstructs the governed representation, reproduces or validates integrity material, compares evidence, records the result, and routes non-match conditions.

Defined

Correction Procedure

Distinguishes Source changes from Anchor-owned errors, preserves prior state, applies the integrity-subject test, Versions same-subject Corrections, and creates new identity where required.

Defined

Publication Procedure

Requires final Validation PASS, confirms Initial Verification and canonical HTML / JSON consistency, applies the formal Publication Gate, assigns publication time, publishes the canonical Version, and preserves prior Versions.

Defined

Maintenance Procedure

Reviews Source, publication, relationships, methods, algorithms, keys, external commitments, and Reverification outcomes after publication.

Defined

Integrity Reference Validation Procedure

Executes Anchor's formal VAL-001 through VAL-042 institutional review in two stages: Structural / Institutional Validation before Initial Verification, and Publication-Readiness Validation before the Publication Gate.

Defined

Operational Flow

Integrity Reference Production
↓
Stage A — Structural / Institutional Validation
↓
Initial Verification
↓
Canonical HTML + Canonical JSON
↓
Stage B — Publication-Readiness Validation
↓
Publication Gate
↓
Published Integrity Reference
↓
Maintenance
↓
Reverification / Correction / Versioning / Lifecycle action as required

Correction Re-entry

Correction
↓
new Anchor Version
↓
Stage A Validation
↓
Reverification
↓
Stage B Publication-Readiness Validation
↓
Publication Gate
↓
new canonical Version

Prior Versions remain preserved throughout.

Procedure Authority

Procedures govern Anchor-owned actions only.

Reference does not transfer authority.

Source Institutions remain authoritative for their Source Artifacts, Source Versions, Source Corrections, and Source lifecycle decisions.

Procedure Discipline

Procedures should be specific enough to execute but should not invent roles, approval bodies, automation permissions, or operational systems before Governance proves they are necessary.

Executable sequence now. Organizational machinery only when needed.

Procedure Records

Future production may prove that procedure executions themselves require structured records or identifiers.

Procedure execution record → possible future object

No Procedure Identifier or execution-record identifier is frozen yet.

First Production Test

The first production Integrity Reference should be treated as a controlled test of these procedures.

Architecture → Procedure → Production → Review → Refine

The goal is not to assume the procedures are perfect before they encounter a real record.

Production Procedures Principle

Architecture defines what Anchor means. Procedures define what Anchor does.

Maintenance → Publication → Corrections → Validation →Verification → Schemas → Back to Anchor →