Anchor · Governance
Governance
Anchor Governance defines how Satoshium Anchor controls its own
Integrity References, integrity methods, representation requirements,
Versions, Corrections, verification practices, publication behavior,
and long-term preservation responsibilities.
Governance establishes responsibility for Anchor-owned decisions
without transferring authority over the external artifacts Anchor references.
Governance Boundary
Anchor governs Anchor.
It does not govern Certifier decisions, Registry records, Chronicle
historical interpretation, Atlas intelligence, Beacon discovery,
Attestor Trust Statements, Navigator workflows, or other Source-System
authority.
Reference does not transfer authority.
Institutional Authority
Anchor is authoritative for its own Integrity References, Anchor identifiers,
Anchor-controlled metadata, Integrity State, Verification Results,
Publication State, Lifecycle State, Versions, Corrections, and procedures.
Foundation
Decision Control
Governance should define how Anchor-specific standards, algorithms,
representation requirements, schemas, Controlled Values, and procedures
are adopted, revised, deprecated, or replaced.
Developing
Change Control
Material changes should be explicit, reviewable, versioned where required,
and implemented without silently rewriting prior integrity history.
Foundation
Accountability
Anchor should preserve who or what process made material institutional
decisions where that information is relevant to later review.
Foundation
Governance Model
Suite Standards → Anchor Standards → Anchor Governance Decisions → Procedures / Schemas / Controlled Values → Production Integrity References → Maintenance / Correction / Versioning
Governance should translate shared Suite expectations and Anchor-specific
integrity requirements into controlled institutional decisions.
Integrity Method Governance
Anchor Governance should control which digest algorithms, signature methods,
timestamp methods, external commitments, and future Bitcoin-based mechanisms
are acceptable for production use.
Representation Governance
Governance should establish requirements for Canonical Representation,
Representation Boundary, canonicalization, reproducibility, and changes
to those requirements.
Schema Governance
Anchor schemas should evolve through explicit Versioning with preserved
compatibility expectations and no silent reinterpretation of earlier
Integrity References.
Controlled Value Governance
Integrity Methods, Integrity States, Verification Results, Publication
States, Lifecycle States, and other governed vocabularies should change
through controlled revision rather than ad hoc usage.
Verification Governance
Governance should define the minimum review required before an Integrity
Reference is accepted for production and the conditions that trigger
later Reverification.
Publication Governance
Governance should define when an Integrity Reference may enter public
production, how publication state changes are recorded, and how withdrawal
or replacement preserves prior lineage.
Versioning Governance
Governance should distinguish Source Artifact Version, Anchor Version,
Schema Version, Algorithm Version, and method Version so one is not
mistaken for another.
Correction Governance
Anchor should correct Anchor-owned errors forward while preserving the
prior state and the reason for material change.
Correct forward. Preserve backward.
Authority Separation
Anchor Governance must preserve the current Suite object model:
Atlas → authoritative intelligence
Certifier → Certification Package
Registry → Satoshium Registry Entry
Chronicle → Chronicle Entry
Anchor → Integrity Reference
Beacon → Discovery Signal / Metadata
Attestor → Trust Statement
Navigator → Workflow Definition
Anchor governance decisions apply to the Integrity Reference and
Anchor-owned operations, not to the authoritative meaning or lifecycle
of the external object.
Source Artifact Changes
A Source Institution may revise, correct, revoke, supersede, republish,
or otherwise change its own artifact.
Anchor Governance should determine the appropriate Anchor response:
No Anchor Action · Reverification · Editorial Maintenance · New Anchor Version · Formal Anchor Correction · New Integrity Reference
External change does not automatically authorize Anchor to rewrite its
historical record.
Decision Records
Material governance decisions should be documented sufficiently to explain:
What changed · Why it changed · Which requirement authorized it · Which Version applies · When it took effect · What prior state remains preserved
Not every routine maintenance action requires a separate governance artifact.
The minimum-necessary-structure principle still applies.
Algorithm and Method Deprecation
Cryptographic methods age.
Anchor Governance should support controlled deprecation when an algorithm,
signature system, timestamp method, or external commitment mechanism is no
longer suitable for new production use.
Deprecation should not erase valid historical Integrity References.
Earlier records should retain enough metadata to preserve their historical
meaning and verification context.
Bitcoin Governance
If Anchor later uses Bitcoin commitments, Governance should define when
Bitcoin is appropriate, which commitment method is approved, how commitments
are recorded, how verification works, and how method changes are handled.
Bitcoin should strengthen Anchor integrity preservation without becoming
the source of institutional authority for the artifact being anchored.
What Anchor Governance Does Not Govern
identity infrastructure
claim meaning
reputation
trust scoring
certification decisions
Registry classification
Chronicle Preservation Eligibility or historical interpretation
Atlas subject intelligence
Beacon discovery significance
Attestor Trust Statement meaning
Navigator workflow authority