The Attestor Identifier architecture establishes stable, canonical identity for Attestor-owned objects while preserving the identifiers and authority of every source object Attestor references.
Identifiers make Attestations and Trust Statements uniquely addressable and traceable across lifecycle, versioning, relationships, validation, publication, and production without turning identity into a claim of truth or authority.
Attestor identifiers provide stable, durable identity for Attestor-owned canonical objects. An identifier identifies the object; it does not by itself establish validity, authority, lifecycle state, publication state, or trustworthiness.
Attestor identifiers must remain institutionally distinguishable from identifiers owned by Atlas, Navigator, Certifier, Registry, Chronicle, Anchor, Beacon, and external authorities. Attestor does not reissue or replace identifiers belonging to referenced source objects.
The canonical Trust Statement identifier family is established as TRST-YYYY-NNNN. The prefix identifies the object as an Attestor Trust Statement, the year records the canonical creation year, and the sequence provides a stable unique number within that year.
The canonical Attestation identifier family is established as ATT-YYYY-NNNN. Attestations are distinct governed Attestor objects and therefore require identities separate from the Trust Statements that may result from their evaluation.
An identifier is assigned only when the corresponding Attestor object reaches canonical Creation. Drafting, candidate preparation, source review, or pre-creation evaluation does not consume or imply a canonical identifier.
Once assigned, an identifier is permanent to the object it identifies. Later lifecycle changes, publication decisions, corrections, version changes, supersession, or withdrawal do not cause the identifier to be reassigned to a different object.
Each canonical Attestor identifier must identify one and only one Attestor object within its identifier family. Duplicate assignment, reuse, or reassignment is not permitted.
Identifiers from source institutions remain source-owned identifiers. Attestor preserves them as governed references exactly enough to resolve and distinguish the referenced object without converting them into Attestor identifiers.
Attestor uses institutionally bounded identifier families. The prefix identifies the Attestor object class, the four-digit year identifies the year of canonical Creation, and the four-digit sequence provides ordered uniqueness within that object family and year.
The identifier architecture preserves the Entry Model's distinction between assertion and conclusion. An Attestation and a Trust Statement are not two states of one identifier. They are distinct governed objects with distinct canonical identities and an explicit relationship between them.
Canonical identifier assignment occurs at Creation, when an Attestor object becomes institutionally recognized as a governed object. Work performed before Creation may prepare or evaluate a candidate, but it does not create a canonical Attestor identity.
An identifier remains attached to its canonical object as that object moves through governed lifecycle and publication states. Versioning may produce distinguishable versions of the same canonical object without assigning the object's identifier to a different object. Whether a material change requires a new object rather than a new version is governed by Versioning and Lifecycle architecture.
Attestor may reference identifiers owned by other Suite institutions or external authorities. Those identifiers remain governed by their source systems and must not be rewritten into the ATT or TRST namespace merely because Attestor evaluates or cites them.
A syntactically valid Attestor identifier proves only that an identifier conforms to the applicable identity pattern when properly assigned. It does not by itself prove that the object is valid, active, published, supported by sufficient evidence, conformant, favorable, current, or trustworthy.
The canonical identifier families and governing semantics are established and production-exercised. Production has demonstrated assignment, persistence, source-identifier preservation, machine validation of canonical representations, and class-specific public addressability. Future allocation, collision-prevention, version-addressing, and other implementation mechanics remain subordinate to Schemas, Validation, Versioning, Publication, and Production.
The first controlled production operation exercised both canonical identifier families. ATT-2026-0001 became the first canonical production Attestation and TRST-2026-0001 became the first canonical production Trust Statement.
The operation did not preallocate production identifiers for representative testing, reuse an identifier, or transfer a source identifier into the Attestor namespace.
Referenced Suite identifiers remained source-owned while the two Attestor objects received their own canonical identities. Publication then made those objects addressable through object-class-specific paths rather than a generic canonical records namespace.
The Identifier architecture is established and production-proven for both Attestor canonical object classes. The first production operation demonstrated assignment at canonical Creation, separation from representative fixtures, persistence through governed change and state transitions, preservation of source-owned identifiers, and class-specific public addressability.
Production proof does not imply that every future sequence-allocation, collision-handling, or version-addressing implementation has been exercised. Identity remains distinct from validation, conformance, lifecycle state, publication, evaluation outcome, and trustworthiness.
Back to Attestor →