Time, states and versions
Support reproducible historical interpretation and traceable corrections while keeping object state, object revision and schema version distinct.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 3 findings · 8 questions
Time axes Separate asserted validity from the history of recorded knowledge.
Valid and recorded time
Describe the valid and recorded intervals of a fact assertion.
Bitemporal fact
Locate a fact assertion on both temporal axes without treating it as independently verified truth.
- For which interval does this record assert that the fact was valid?
- When did this assertion enter the records, and when was it superseded there?
- What does this record assert as valid at the specified valid time under the specified recorded-time cutoff?
Revisions and states Distinguish corrections, domain lifecycle states and schema conformance.
Revision and correction
Describe corrections while preserving traceable revision identity.
Retroactive correction
Identify a correction and the earlier assertion it changes.
- Which uniquely identified revision does this correction record reference, and which valid interval does it change?
- Is the prior revision referenced by this correction still retrievable?
State and schema version
Keep domain lifecycle meaning separate from data structure versions.
State versus schema
Record the applicable domain state and schema binding independently.
- Which domain defines the lifecycle state recorded for this object?
- Which schema version does this object record conform to independently of its state?
- Does the archive record for this object preserve its full history?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise contract
- Entry kind
- contract
- Domain
- EnterpriseXCT
- Industry
- Cross-industry
- Tags
- EM-XCT-04W0contractTemporalValidityRevisionLifecycleTransitionSchemaBinding
What it is Filled
A shared contract for valid time, recorded time, revisions, states and schema versions without a universal domain lifecycle.
Why it exists Filled
Support reproducible historical interpretation and traceable corrections while keeping object state, object revision and schema version distinct.
Distinguishing features Filled
- Valid time, when something was true, is kept apart from recorded time, when it was known.
- A schema version describes the shape of the data, while an object revision describes a change to one object.
- Lifecycle states belong to their domain; no universal lifecycle is imposed on all objects.
- Archiving changes availability and never destroys history.
What robots and AI may and may not do Filled
Must not
- Use a single version or active field to stand for both the schema version and the object state.
- Overwrite past values when applying a retroactive correction.
- Treat recorded time as the time the fact became true.
- Delete history when an object is archived.
- Impose one lifecycle on objects from different domains.
- Present a recorded assertion as independently established truth solely because it has temporal metadata.
- Delete history without explicit authorization or contrary to retention requirements or applicable holds.
Only with a human decision
- Approve retroactive corrections that affect pay, obligations or filed reports.
- Authorize history deletion after checking retention requirements and applicable holds.
- Approve migration to a schema version with changed meaning.
May
- Answer as-of questions about recorded assertions using both valid time and recorded time.
- Apply late corrections as new revisions with the affected valid interval.
- Report the schema version and the domain state of an object separately.
- Flag records that use one field for both version and state.
Moral aspects Filled
- Retroactive changes can alter what people were paid or owed, so prior knowledge must stay visible.
- Accurate time records protect people and organisations in disputes and audits.
Who is affected
- People whose records are corrected
- Auditors and regulators
- Consumers of historical reports
Owners Filled
Steward
An enterprise records governance steward oversees temporal integrity and coordinates the accountable owners of instance histories and schema definitions.
Master systems
- Operational systems of record own enterprise object revisions and temporal fact histories.
- Records management repositories own retained historical records under declared custody.
- Schema registries own schema definitions and versions separately from instance histories.
- Policy repositories own retention requirements and applicable hold rules.
Links to other meta-models Filled
references
- WM-XCT-009 - conceptual-candidate
- WM-XCT-021 - conceptual-candidate
- WM-XCT-022 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- An object revision has an identifier unique within its object history even when recorded timestamps coincide.
- A schema binding is identified by schema identifier and version.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- A temporal record carries valid-from, valid-to, recorded-from and recorded-to or equivalent fields.
- A temporal record is distinguishable from an audit log or a single last-modified timestamp.
Capabilities and actions required Filled
- Reports can reproduce assertions recorded as valid under a specified historical knowledge cutoff.
- Late corrections can be represented without losing prior recorded assertions.
Hazards and failure modes required Filled
- Conflating schema version and object state makes historical interpretation ambiguous.
- Time zone loss can shift intervals across dates.
- Archiving or migration can cause unintended history loss.
- Coincident timestamps can cause revision identity collisions if timestamps are the sole identifiers.
Standards and interfaces optional Filled
- ISO 8601 from the International Organization for Standardization describes representations of dates, times and intervals.
- ISO/IEC 9075 from the International Organization for Standardization and the International Electrotechnical Commission specifies SQL features including temporal tables.
- OWL-Time from the World Wide Web Consortium describes temporal entities and intervals.
Context of use required Filled
- Temporal records support domains where facts change and late corrections occur.
- Audits and disputes may require reconstruction of assertions available at a past recorded time.
Sources Filled
- 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
- W3C Time Ontology in OWL - Checked live (HTTP 200) on 2026-10-07.
- Semantic Versioning 2.0.0 - Checked live (HTTP 200) on 2026-10-07.
Open questions
- What was true, and what was known, as of a given date?
- How to correct retroactively?
- Which states belong to a specific domain?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-xct-04/brief.json, ver-cy/world-models/card-supplements/em-xct-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.