Chronoscript Semantic Profiles

PURPOSE

Chronoscript separates a stable canonical record type from a versioned semantic profile. This allows new use cases without changing the meaning of previously finalized records.

CORE TYPE

The fundamental record type expresses the broad canonical nature of the record (for example EVENT, DECLARATION, PUBLICATION or CORRECTION).

SEMANTIC PROFILE

A profile is identified by a namespaced Profile ID and Profile Version, declares the compatible core type and may validate structured extension data. Every finalized record retains the exact profile ID and version used at finalization. A newer profile version never rewrites an older record. Deprecated profiles remain identifiable for historical interpretation.

NAMESPACES

LXKeys-owned profiles use the lxkeys.* namespace. Future third-party profiles must use a controlled namespace and become available only after profile registration and validation.

EXTENSIBILITY

New semantic profiles can be registered without multiplying fundamental record types. Canonical identity, sequence, time coordinates, finality, integrity metadata and profile reference remain part of the stable envelope.

PROFILE IMMUTABILITY
A registered Profile ID + Profile Version is a historical interpretation contract. Its core type, validation schema and descriptive definition are immutable. Lifecycle status may only move forward from active to deprecated or retired. A semantic change requires a new profile version.

USER INTERFACE BOUNDARY
Manual daily entry does not ask the operator to choose Profile ID, Profile Version or raw extension JSON. LXKeys resolves the compatible generic profile from the fundamental type. Specialized workflows and API submissions may select a registered compatible profile; business fields are validated against its schema.

REGISTRY PUBLICATION
A Registry Edition publication uses fundamental type PUBLICATION with profile lxkeys.registry.publication@1.0.0. No dedicated registry-publication fundamental type is required.