Attestation Schema
Structural schema for a canonical governed, attributable Attestation using the ATT-YYYY-NNNN identifier family.
Attestor · Operational Schemas
Schemas
This area defines the structural schema layer through which adopted Attestor architecture is expressed for implementation, authoring, executable validation, and production use. The canonical ATT/TRST object contracts have now been exercised by the first controlled production operation.
Canonical responsibility: Attestor → Trust Statement
Schema hierarchy: Architecture → Schema/Profile → Template → Governed Instance
Governing principle: Reference does not transfer authority.
Schema hierarchy: Architecture → Schema/Profile → Template → Governed Instance
Governing principle: Reference does not transfer authority.
Trust Statement Schema
Structural schema for Attestor's canonical institutional output: a governed, attributable, bounded conclusion using the TRST-YYYY-NNNN identifier family.
Evidence Attestation Profile
Specialized schema profile for the adopted evidence Attestation Type. Evidence informs evaluation but does not automatically establish proof or a Trust Statement.
Source / Provenance Attestation Profile
Specialized schema profile for the adopted source-provenance Attestation Type, preserving provenance, relevant source state, and authority context.
Correction / Change Profile
Governed change structure used with Lifecycle and Versioning. Correction does not become a separate canonical object class merely because a change profile exists.
Trust Signal — Legacy
Historical design artifact only. Trust Signal is not a canonical Attestor object, identifier family, score, reputation mechanism, or production schema.
First Production Schema Demonstration
The first controlled production operation exercised the canonical Attestation and Trust Statement object contracts through real production instances: ATT-2026-0001 and TRST-2026-0001. Their final canonical representations preserved identifier, version, lifecycle state, publication state, authority/provenance context, relationships, scope, limitations, and the governed assertion or conclusion required by their respective object classes.
ATT-2026-0001 → Canonical Attestation contract exercised
TRST-2026-0001 → Canonical Trust Statement contract exercised
Version → V1.0
Lifecycle → Active
Publication → Published
Structured relationships → Exercised
Final-state Validator v0.5 → VALID for both objects
Base ATT / TRST schema architecture → DEMONSTRATED IN PRODUCTION
TRST-2026-0001 → Canonical Trust Statement contract exercised
Version → V1.0
Lifecycle → Active
Publication → Published
Structured relationships → Exercised
Final-state Validator v0.5 → VALID for both objects
Base ATT / TRST schema architecture → DEMONSTRATED IN PRODUCTION
The production operation also exercised correction of relationship serialization before final publication. Structured relationship blocks replaced descriptive relationship strings while canonical identity and substantive meaning were preserved, demonstrating that schema-conformant representation remains subordinate to governed object identity and Versioning.
Schema and Validation Boundary
Schemas define the canonical structural contract. Validation tests applicable normative requirements against an object and its execution context. Production use demonstrated both layers without collapsing them: schema representation did not itself determine Eligibility, Evaluation Outcome, Conformance, Publication, or truth.
Schema → Structural contract
Validation → Applicable rule testing
Conformance → Separate determination
Evaluation → Separate institutional act
Schema Conformance / Validity ≠ Evaluation Outcome
Valid ≠ Published
Schema Representation ≠ Universal Truth
Validation → Applicable rule testing
Conformance → Separate determination
Evaluation → Separate institutional act
Schema Conformance / Validity ≠ Evaluation Outcome
Valid ≠ Published
Schema Representation ≠ Universal Truth
Canonical Schema Relationship
Eligible Governed Inputs → Attestation → Rule-Constrained Evaluation → Trust Statement
The schema layer implements architecture already established by Attestor. Canonical identity, controlled values, authority, provenance, eligibility, evaluation, relationships, lifecycle, versioning, validation, conformance, publication, and methodology remain governed by their respective Attestor specifications.
Schema Architecture → Established and Production-Proven
Base Attestation Schema → Production-exercised
Base Trust Statement Schema → Production-exercised
Canonical ATT/TRST structured representation → Exercised
Lifecycle / publication fields → Exercised
Version identity → Exercised
Structured relationships → Exercised
Executable validation alignment → Demonstrated with Validator v0.5
Evidence / Source-Provenance specialized profiles → Remain profile-specific reconciliation work unless separately completed
Trust Signal schema → Legacy / noncanonical
Production proof → ESTABLISHED for base ATT/TRST contracts
Base Attestation Schema → Production-exercised
Base Trust Statement Schema → Production-exercised
Canonical ATT/TRST structured representation → Exercised
Lifecycle / publication fields → Exercised
Version identity → Exercised
Structured relationships → Exercised
Executable validation alignment → Demonstrated with Validator v0.5
Evidence / Source-Provenance specialized profiles → Remain profile-specific reconciliation work unless separately completed
Trust Signal schema → Legacy / noncanonical
Production proof → ESTABLISHED for base ATT/TRST contracts
Production proof is intentionally bounded to the base canonical Attestation and Trust Statement contracts and the structures exercised by the first operation. It does not imply that every specialized profile, optional field combination, or future serialization path has been production-tested.
Back to Attestor →