EM-XCT-04 · Shared contract · W0
Time, states and versions
A shared contract for valid time, recorded time, revisions, states and schema versions without a universal domain lifecycle.
Partially published; research continues
Claude: independent-study-and-three-static-audits-complete-final-accept-with-limits; Grok: independent-study-and-published-code-audit-complete-accept.
Published results
Research note, in Russian: host domain transitions and payload validation; civil/uncertain time adapters; durable conflicts, concurrency and scope registry; retention/erasure; production capacity/rollover and existing-Dimension migration; all broad parent research holds.
Subject boundary and candidate types
- TemporalValidity
- Revision
- LifecycleTransition
- SchemaBinding
Deep research questions
- What was true, and what was known, as of a given date?
- How to correct retroactively?
- Which states belong to a specific domain?
Verifiable invariants
- Schema version is not object revision
- Valid time is not recorded time
- Archiving does not destroy history
End-to-end acceptance scenario
A late correction of an assignment gives different as-of valid and as-known answers without losing prior knowledge.
Negative case
A single version=active stands in for both the schema version and the state.
Approaches to compare
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
Candidates in the live catalogue
- WM-XCT-009 · Time / Calendar · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-021 · Lifecycle / Status · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-022 · Version / Change History · 0.3.0-research.2 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.