Record Models
Defines the common structures used for certifications, attestations, evidence, registry records, references, verification objects, and canonical machine-readable representations.
Architecture ActiveSuite · Standards
Schemas Standard
The Schemas Standard defines how Satoshium structured records, certification objects, evidence records, attestations, registry entries, and discovery data are organized across the Suite.
Schemas make Satoshium records readable by both humans and machines while preserving meaning, consistency, and long-term interoperability.
Required Fields
Establishes the minimum fields needed for each record type to remain valid, understandable, and verifiable across the Suite.
PlannedValidation Rules
Defines how structured records are validated before publication, registry inclusion, certification use, integrity processing, or external consumption.
Architecture ActiveSchema Evolution
Provides a framework for versioning, extending, and preserving schemas as Suite tools and certification methods mature over time.
Architecture ActiveStandard Role
The Schemas Standard provides the structural language that allows Satoshium records to be created, validated, exchanged, preserved, and interpreted consistently across every Suite subsystem.
A record without structure may be readable. A record with a schema can become
portable, verifiable, and durable.
Canonical JSON Standard
When a Satoshium Suite record declares or requires a canonical JSON representation, the Suite-wide canonicalization rule is:
Representation Type → canonical_json
Canonicalization Standard → RFC 8785 — JSON Canonicalization Scheme (JCS)
Character Encoding → UTF-8
Canonicalization Standard → RFC 8785 — JSON Canonicalization Scheme (JCS)
Character Encoding → UTF-8
JCS provides deterministic serialization so semantically equivalent JSON data is not treated as different merely because of indentation, insignificant whitespace, or object-member presentation order.
A Suite institution may use another representation type where appropriate, but it must not label a representation canonical_json while applying a conflicting local canonicalization rule.
Suite-Wide Rule DefinedInstitutional Profiles
Suite institutions may define narrower schema profiles when production requires additional constraints, provided those profiles remain compatible with the Suite-wide schema rules.
Suite Schema Standard
↓
Institution-specific Schema / Profile
↓
Production Record
↓
Institution-specific Schema / Profile
↓
Production Record
Anchor's first production Integrity Reference therefore inherits the Suite definition of canonical_json rather than inventing an Anchor-specific JSON normalization rule.