Chronoscript Protocol Public Reference

PUBLIC REFERENCE — NON-NORMATIVE

Chronoscript defines a controlled path from preparation to canonical registration. Information may be entered manually or prepared from a documented JSON or structured-text source. An imported source is normalized and reviewed before it becomes a mutable Chronoscript draft. Import, parsing and submission never create a canonical Registry Record by themselves.

The lifecycle is DRAFT → SUBMITTED → VALIDATION → READY FOR FINALIZATION → FINALIZED. Finalization is the only step that assigns a permanent Record ID and Registry Sequence. The current controlled record types are EVENT, DECLARATION, PUBLICATION and CORRECTION.

DRAFT is the only workflow state in which record content and the evidence set may be changed. SUBMITTED, VALIDATION and READY FOR FINALIZATION are read-only states. Any amendment after submission requires an explicit return to DRAFT, followed by a new submission and review cycle. Workflow transitions are recorded in the administrative audit trail.

Before READY FOR FINALIZATION, the applicable validation profile checks required fields, controlled values and internal consistency. When Event UTC is present, Event DYPCLT is calculated from the UTC date and any conflicting supplied DYPCLT value is rejected. Validation is repeated immediately before finalization.

A finalized record is append-only and read-only. It is not silently edited or deleted. A correction is represented by a later linked record. Event UTC / Event DYPCLT describe the event when available; Registration UTC / Registration DYPCLT describe canonical registration; Registry Sequence describes canonical order.

Public integration interfaces expose what is required to prepare compatible submissions, inspect the canonical sequence and verify published records. Canonical finalization remains a controlled LXKeys Core function.