Profile Role
The Profile adds only certification-specific requirements to the universal Chronicle Entry structure. It does not create a separate canonical Certification Event object.
Chronicle · Schemas · Event-Type Profile
Certification Event-Type Profile
The Certification Event-Type Profile is Chronicle's first production Event-Type Profile. It specializes the Chronicle Base Schema for Chronicle Entries that preserve qualifying certification-related Occurrences.
Certifier remains authoritative for certification determinations, Certification Packages, lifecycle actions, and certification status. Chronicle owns the historical-preservation record representing the qualifying Occurrence.
Base Schema Relationship
Certification-related Entries remain governed by the Chronicle Base Schema and inherit all universal Entry requirements.
Chronicle Base Schema + Certification Event-Type Profile = Certification-related Chronicle Entry
Authority Boundary
The Profile requires durable reference to the authoritative Certifier record, but does not duplicate Certification Package findings, evidence, schema, determination logic, or lifecycle mechanics.
Profile Version
The initial Certification Event-Type Profile version is:
1.0.0
Required Certification Constraints
In addition to the universal Chronicle Base Schema requirements, this Profile requires or strengthens the following certification-specific fields and rules.
event_type_profile = certification-event-profile
originating_system = certifier
event_type = approved Certification Event Type
event_date = non-null certification Occurrence date or timestamp
authoritative_record_references = minimum one authoritative Certifier reference
provenance = includes authoritative certification reference
originating_system = certifier
event_type = approved Certification Event Type
event_date = non-null certification Occurrence date or timestamp
authoritative_record_references = minimum one authoritative Certifier reference
provenance = includes authoritative certification reference
Approved Certification Event Types
Certification Created
Certification Renewed
Certification Suspended
Certification Revoked
Certification Expired
Certification Renewed
Certification Suspended
Certification Revoked
Certification Expired
Machine-readable values are governed through Chronicle Controlled Values.
Authoritative Certification Reference
Every Entry governed by this Profile must identify the authoritative Certifier record establishing the represented Occurrence.
Chronicle Entry → references → Certification Package
Originating System
This Profile requires:
originating_system: certifier
The field is conditional in the Base Schema and required only because this Profile establishes the operational need.
Related Registry Reference
A related SREG reference becomes required when a corresponding Registry Entry exists and is materially relevant to the Chronicle Entry.
Registry remains authoritative for the SREG.
Historical Context
Historical Context explains the certification Occurrence within Satoshium institutional history without restating Certifier-owned findings or determination logic.
Provenance
Certification Provenance should preserve Certifier origin, acquisition or access method, retrieval date, authoritative record reference, and material limitations where applicable.
Verification
Chronicle verifies its own historical representation, including identifiers, Event Date, Certifier origin, references, Relationships, Provenance, and limitations. It does not re-adjudicate the certification determination.
What the Profile Does Not Duplicate
Certification findings · Certification evidence body · Certification Package schema ·
Certification determination logic · Certifier validation structures ·
Certification lifecycle mechanics
Chronicle preserves references and historical meaning rather than reproducing authoritative Certifier structures.
Profile Artifacts
The Certification Event-Type Profile is published through a human-readable specification and a machine-readable JSON Schema implementation.
certification-event-profile.md → Human-readable production specification
certification-event-profile.json → Machine-readable validation profile
Open Markdown Specification →
Open JSON Profile →
certification-event-profile.json → Machine-readable validation profile
Validation Architecture
A production certification-related Chronicle Entry is validated through the two-layer schema model:
chronicle-base-schema.json
+
certification-event-profile.json
=
Certification-related Chronicle Entry Validation
+
certification-event-profile.json
=
Certification-related Chronicle Entry Validation
Validation confirms conformance. Verification remains a separate Chronicle review of historical representation.
First Production Application
The Certification Event-Type Profile Version 1.0.0 now has a production precedent. On August 22, 2026, it governed CHR-2026-0001 Entry Version 1, preserving the July 5, 2026 issuance of SC-CERT-2026-0001.
Event Type: certification_created
Originating System: certifier
Authoritative Reference: SC-CERT-2026-0001
Related Registry Entry: SREG-2026-0001
Subject: Atlas Jurisdiction Record — El Salvador
Base + Profile Conformance: PASS
Chronicle Validation: PASS
Publication Gate: APPROVED
Publication State: published
Originating System: certifier
Authoritative Reference: SC-CERT-2026-0001
Related Registry Entry: SREG-2026-0001
Subject: Atlas Jurisdiction Record — El Salvador
Base + Profile Conformance: PASS
Chronicle Validation: PASS
Publication Gate: APPROVED
Publication State: published
The production application required no change to the Profile's machine-readable validation semantics.
Open CHR-2026-0001 →Profile Philosophy
Event-Type Profiles should add the minimum specialized structure necessary for operational accuracy while preserving one canonical Chronicle Entry model.
Base Schema defines the Chronicle Entry. The Certification Event-Type Profile supplies only the certification-specific requirements.
Back to Chronicle Schemas →