Schema defines the structured formats used by Satoshium Certifier to represent Certification Packages, generated artifacts, evidence inventories, certified records, and Suite-ready references.
Suite Standards define the meaning of certification. Suite Methodology defines the process. Certifier schemas preserve the operational records produced when that process is executed.
Suite Standards → Suite Methodology → Operations Toolkit →The Certification Package schema defines Certifier’s canonical operational record, including the Certification Subject, Profile, Scope, applicable Suite Standards, applicable Suite Methodology, Evidence Inventory, evaluation, certification decision, generated artifacts, lifecycle state, and certification history.
The SCRD JSON schema defines the machine-readable serialization of the canonical Certified Record generated from the Certification Package. It supports public indexing, Registry integration, structured exchange, future APIs, and long-term interoperability without creating a separate certification object.
The Evidence Inventory schema organizes the factual materials associated with a Certification Package, including Evidence Record identifiers, source references, evidence types, traceability notes, review status, integrity references, and mapped Suite Standards requirements.
Schema conventions define the fields used by generated certification artifacts, including the Certification Process Report (SCPR), Certification Receipt (SCR), Certified Record HTML representation, Certified Record JSON serialization, Evidence Maps, and related Suite-ready references.
Structured reference stubs prepare certification records for Registry cataloging, Chronicle preservation, Anchor integrity references, Beacon discovery metadata, Attestor verification support, and Navigator workflow orchestration.
Schemas should be versioned so historical certification records remain understandable even when newer schema versions, stronger validation rules, or additional Suite integrations are introduced.
Certifier schema begins with the Certification Package as Certifier’s canonical operational record. Evidence structures, generated artifacts, Certified Record representations, and Suite-ready references derive from that Package without becoming independent certification decisions.
Schema is Certifier’s structural record layer. Documentation explains the system, the SCPR preserves certification reasoning, the SCR provides public confirmation, and the SCRD preserves the canonical Certified Record through human-readable HTML and machine-readable JSON representations.
The initial schema focus is the Certification Package and the evidence structures, generated artifacts, Certified Record representations, and Suite-ready references derived from it. The Operations Toolkit supports this architecture by generating and validating repository-based artifact sets without replacing certification judgment or operating as an independent certification authority.