Purpose
The Certification Event-Type Profile specializes the Chronicle Base Schema for certification-related Occurrences. It adds only the requirements necessary to preserve certification history while maintaining Suite authority boundaries.
Chronicle · Certification Event-Type Profile
Satoshium Chronicle Certification Events
The Certification Event-Type Profile defines the certification-specific requirements applied to Chronicle Entries that preserve qualifying certification-related Occurrences. The Profile specializes the Chronicle Base Schema and participates directly in Chronicle Verification, Validation, publication, and preservation.
Certifier remains authoritative for certification determinations, Certification Packages, lifecycle actions, and certification status. Chronicle owns the historical-preservation record representing the qualifying certification Occurrence and preserves that history by referencing the authoritative Certifier record rather than duplicating it.
Core Distinction
Certifier owns the authoritative certification action and Certification Package. Registry owns any related SREG Registry Entry. Chronicle owns the Chronicle Entry that preserves the qualifying historical Occurrence and its historical context.
Base Schema Relationship
Certification-related Chronicle Entries remain canonical Chronicle Entries. The Certification Event-Type Profile specializes the Base Schema; it does not create a separate canonical Certification Event object.
Chronicle Base Schema + Certification Event-Type Profile = Certification-related Chronicle Entry
Authority Boundary
The Profile may require references to authoritative Certifier records, but it does not reproduce certification findings, evidence packages, status mechanics, or other Certification Package contents owned by Certifier.
Historical Meaning
A Chronicle Entry classified under this Profile preserves what happened, when it happened, which Certifier record establishes the Occurrence, and the historical context needed to understand the Occurrence over time.
Reference-Based Interoperability
Chronicle references Certification Packages, related Registry Entries where materially relevant, Integrity References, Trust Statements, public records, or other Suite objects without redefining their schemas or transferring their institutional authority.
Certification Event Types
The Certification Event-Type Profile applies to the approved certification-related Event Types when the represented Occurrence satisfies Chronicle Preservation Eligibility and can be tied to an authoritative Certifier record.
Certification Created → Certification Renewed → Certification Suspended →
Certification Revoked → Certification Expired
Certification Created
A Chronicle Entry classified as Certification Created preserves the historical Occurrence in which Certifier created a new authoritative Certification Package. Chronicle references that Package; it does not recreate the certification determination.
Certification Renewed
A Chronicle Entry classified as Certification Renewed preserves the historical Occurrence in which Certifier authoritatively renewed a certification under the applicable certification rules and lifecycle model.
Certification Suspended
A Chronicle Entry classified as Certification Suspended preserves the historical Occurrence in which Certifier authoritatively placed a certification into a suspended state.
Certification Revoked
A Chronicle Entry classified as Certification Revoked preserves the historical Occurrence in which Certifier authoritatively revoked a certification.
Certification Expired
A Chronicle Entry classified as Certification Expired preserves the historical Occurrence in which a certification reached an expired state under the applicable Certifier rules and lifecycle model.
Future Event Types
Additional certification-related Event Types should be added only when they correspond to authoritative Certifier actions or states and are approved through Chronicle Event Type and Controlled Values governance.
What the Profile Requires
The Certification Event-Type Profile uses the Chronicle Base Schema and adds or strengthens only certification-specific requirements.
event_type_profile = certification-event-profile ·
Approved Certification Event Type · Non-null Event Date / Time ·
originating_system = certifier ·
authoritative_record_references · Historical Context ·
Certification-Specific Provenance
At least one authoritative reference must be structured so that it identifies both the referenced certification object and system: certifier. A related Registry identifier is required only when a corresponding SREG Registry Entry exists and is materially relevant to the Chronicle Entry.
Inherited from the Chronicle Base Schema
Certification-related Chronicle Entries inherit the universal Base Schema fields and structures governing Chronicle identity, Versions, historical representation, Provenance, Verification, Lifecycle, Publication, and Entry creation.
entry_id · schema_id · schema_version · entry_version · title · summary ·
event_type · event_date · historical_context · provenance · verification_state ·
lifecycle_state · publication_state · entry_created_at
What the Profile Does Not Duplicate
The Certification Event-Type Profile does not reproduce the internal contents of the Certification Package.
Certification findings · Certification evidence body · Certification Package schema ·
Certification determination logic · Certifier lifecycle mechanics
Those remain within Certifier. Chronicle preserves durable references and the historical meaning of the qualifying Occurrence.
Relationship to Registry
Registry creates and maintains independent SREG Registry Entries. A certification-related Chronicle Entry may reference the related SREG when one exists, but Registry remains authoritative for the catalog record and Registry lifecycle state.
Certifier owns the certification record.
Registry owns the catalog record.
Chronicle owns the historical-preservation record representing the qualifying Occurrence.
Reference does not transfer authority.
Registry owns the catalog record.
Chronicle owns the historical-preservation record representing the qualifying Occurrence.
Reference does not transfer authority.
Verification
Chronicle Verification reviews Chronicle's historical representation, including authoritative references, Event Date, Registry references where applicable, Relationships, Provenance, Historical Context, Sources, Evidence, and material limitations. Formal identifier, schema, and Profile conformance are tested by Validation.
Verification does not re-adjudicate the certification determination made by Certifier.
Validation
Certification-related Chronicle Entries are validated against both the Chronicle Base Schema and the Certification Event-Type Profile, together with the applicable institutional Chronicle Validation Rules.
Base Schema PASS + Certification Event-Type Profile PASS + Applicable CHR-VAL Rules PASS = Chronicle Validation PASS
Validation confirms, among other requirements, the approved certification Event Type, non-null Event Date, originating_system = certifier, authoritative Certifier reference, Controlled Values, Provenance, Relationships, Verification dependency, authority boundaries, and publication readiness.
Validation FAIL means Chronicle's current certification-related representation does not yet conform. It does not invalidate the Certifier determination or establish that the certification Occurrence is false.
Corrections and Versioning
If Chronicle later discovers that its own certification-related Entry is materially wrong, Chronicle corrects and Versions its own record according to Chronicle Correction and Versioning rules, followed by Reverification and Revalidation where required.
If Certifier later performs a distinct certification action, that later action may constitute a new qualifying Occurrence and therefore a new Chronicle Entry rather than a rewrite of the earlier historical record.
Certification Entry Production Path
Certification-related Entries follow the same Chronicle Entry Production Procedure as every other Chronicle Entry, with the Certification Event-Type Profile adding its specialized requirements.
Identify Certification Occurrence → Assess Preservation Eligibility → Collect Certifier Reference →
Classify Certification Event Type → Select Certification Event-Type Profile →
Assign Chronicle Identifier → Create Entry → Establish Relationships →
Record Sources / Evidence / Provenance → Verify → Validate →
Publication Gate → Approve / Withhold Publication → Publish when approved → Preserve
Publication Gate
A certification-related Chronicle Entry may proceed toward publication only when the required Verification State is satisfied, Chronicle Validation = PASS, required authoritative Certifier references are present, and all applicable publication prerequisites are satisfied.
Required Verification State + Validation PASS + Required Certifier Reference + Publication Prerequisites = Eligible to Proceed to the Publication Gate
Publication preserves Chronicle's historical Entry. It does not republish the Certification Package as a Chronicle-owned object.
First Production Certification Entry
The Certification Event-Type Profile has now been exercised in production through CHR-2026-0001.
Chronicle Entry: CHR-2026-0001
Event Type: certification_created
Event-Type Profile: certification-event-profile 1.0.0
Originating System: certifier
Authoritative Certification Reference: SC-CERT-2026-0001
Related Registry Entry: SREG-2026-0001
Subject: Atlas Jurisdiction Record — El Salvador
Verification: verified
Validation: PASS
Publication Gate: APPROVED
Publication State: published
Event Type: certification_created
Event-Type Profile: certification-event-profile 1.0.0
Originating System: certifier
Authoritative Certification Reference: SC-CERT-2026-0001
Related Registry Entry: SREG-2026-0001
Subject: Atlas Jurisdiction Record — El Salvador
Verification: verified
Validation: PASS
Publication Gate: APPROVED
Publication State: published
The production Entry preserves the July 5, 2026 certification-created Occurrence. It does not own the certification action, duplicate the Certification Package, or convert the related Registry Entry into certification authority.
Open CHR-2026-0001 →Profile Philosophy
The Certification Event-Type Profile gives Chronicle the minimum additional structure necessary to preserve certification history without creating a competing certification system or duplicating Certifier-owned records.
Certifier establishes certification authority. Chronicle preserves the historical record of what occurred.
Schema defines structure. Verification reviews the representation. Validation tests conformance. Publication determines public production state.
Open Certification Event-Type Profile →
Open Validation →
Back to Chronicle →
Schema defines structure. Verification reviews the representation. Validation tests conformance. Publication determines public production state.