Enterprise Temporal History
Record effective timelines, preserve earlier recorded views and bind schemas and domain states without rewriting history.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 22 findings · 22 questions
Scope and interpretation Scope and interpretation with explicit uncertainty and host responsibility.
Identity and boundaries
Identity and boundaries for one governed temporal assertion scope.
What is the governed fact scope?
What is the governed fact scope?
- What is the governed fact scope? governed-context
What survives a rename, transfer or split?
What survives a rename, transfer or split?
- What survives a rename, transfer or split? governed-context
Can two masters or values apply simultaneously?
Can two masters or values apply simultaneously?
- Can two masters or values apply simultaneously? governed-context
Schema and state bindings
Schema and state bindings for one governed temporal assertion scope.
Which schema interprets this value?
Which schema interprets this value?
- Which schema interprets this value? governed-context
Which status axis and vocabulary are in use?
Which status axis and vocabulary are in use?
- Which status axis and vocabulary are in use? governed-context
Did a legitimate domain transition occur?
Did a legitimate domain transition occur?
- Did a legitimate domain transition occur? governed-context
Effective and recorded history Effective and recorded history with explicit uncertainty and host responsibility.
Effective intervals
Effective intervals for one governed temporal assertion scope.
What is recorded as effective on the selected date?
What is recorded as effective on the selected date?
- What is recorded as effective on the selected date? governed-context
Does the exact endpoint belong to this interval?
Does the exact endpoint belong to this interval?
- Does the exact endpoint belong to this interval? governed-context
What do uncovered periods or an empty snapshot mean?
What do uncovered periods or an empty snapshot mean?
- What do uncovered periods or an empty snapshot mean? governed-context
Receipts and corrections
Receipts and corrections for one governed temporal assertion scope.
What had this timeline host recorded by a cutoff?
What had this timeline host recorded by a cutoff?
- What had this timeline host recorded by a cutoff? governed-context
Which of two same-second receipts is intended?
Which of two same-second receipts is intended?
- Which of two same-second receipts is intended? governed-context
How does a late correction preserve earlier answers?
How does a late correction preserve earlier answers?
- How does a late correction preserve earlier answers? governed-context
Authority and controlled operations Authority and controlled operations with explicit uncertainty and host responsibility.
Write integrity
Write integrity for one governed temporal assertion scope.
Was this retry already applied?
Was this retry already applied?
- Was this retry already applied? governed-context
Is this write based on the current head?
Is this write based on the current head?
- Is this write based on the current head? governed-context
Who may assert this scope now?
Who may assert this scope now?
- Who may assert this scope now? governed-context
Historical disclosure
Historical disclosure for one governed temporal assertion scope.
May this role read historical data for this purpose?
May this role read historical data for this purpose?
- May this role read historical data for this purpose? governed-context
Does a pinned assertion establish truth or permission?
Does a pinned assertion establish truth or permission?
- Does a pinned assertion establish truth or permission? governed-context
Adoption and continuity Adoption and continuity with explicit uncertainty and host responsibility.
Archival and import
Archival and import for one governed temporal assertion scope.
What changes when this timeline is archived?
What changes when this timeline is archived?
- What changes when this timeline is archived? governed-context
How can an imported history avoid forged local knowledge?
How can an imported history avoid forged local knowledge?
- How can an imported history avoid forged local knowledge? governed-context
Which precision or calendar adapter is required?
Which precision or calendar adapter is required?
- Which precision or calendar adapter is required? governed-context
Composition and migration
Composition and migration for one governed temporal assertion scope.
What is the minimum useful Company Dimension setup?
What is the minimum useful Company Dimension setup?
- What is the minimum useful Company Dimension setup? governed-context
Can we migrate or export without losing recorded history?
Can we migrate or export without losing recorded history?
- Can we migrate or export without losing recorded history? governed-context
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Cross-cutting context
- Entry kind
- companion-contract
- Navigation path
- NAV.XCT
- Domain
- EnterpriseTemporal historyLifecycle
- Industry
- Cross-industry
- Tags
- EM-XCT-04temporalhistorybitemporalschemalifecycle
- Also called
- Bitemporal fact history, EM-XCT-04, Time, states and versions
What it is Filled
A companion contract for a Company Dimension that records when facts were valid in the business and when the company recorded them, keeps earlier recorded views reproducible, and binds schemas and domain states to time.
Why it exists Filled
Record effective timelines, preserve earlier recorded views and bind schemas and domain states without rewriting history.
Distinguishing features Filled
- Keeps two clocks: when something was true in the business and when the company recorded it.
- Corrects by appending a new recorded snapshot, so earlier answers can be reproduced.
- Uses half-open validity intervals and rejects overlaps within one scope.
What robots and AI may and may not do Filled
Must not
- Rewrite or delete an earlier recorded view.
- Return false when the honest answer is insufficient context.
- Choose silently between two timelines for the same scope.
Only with a human decision
- Deciding which of two conflicting timelines is authoritative.
- Creating a new scope when meaning changes.
May
- Answer what was valid at a time as recorded at another time.
- Append a corrected snapshot.
- Return unknown before the first receipt.
Moral aspects Filled
- History that can be rewritten lets mistakes about people disappear; append-only records keep accountability.
- Old attribution stays visible, so people are judged by what was known at the time.
Who is affected
- Employees and contractors whose actions or data appear in company records
- Customers, suppliers and partners named in company records
- Auditors, regulators and courts that rely on the record later
Owners Filled
Steward
Each domain owner owns the history of its facts; the host operator owns the recorded-time ledger.
Master systems
- Bitemporal store or ledger of the host
Links to other meta-models Filled
references
- WM-XCT-009 - 0.3.0-research.1
- WM-XCT-021 - 0.3.0-research.1
- WM-XCT-022 - 0.3.0-research.2
aligned
- vr.wm-xct-009
- vr.wm-xct-021
- vr.wm-xct-022
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Timeline scope ID.
- Recorded snapshot sequence number.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: it has no physical body to measure.
Recognition optional Filled
- A history record carries validFrom/validTo and a recorded sequence for one scope.
Capabilities and actions required Filled
- Compare exact references; request missing context
- Keep stable scope; create a new governed scope when meaning changes
- Separate scopes; request an authority decision, never silently choose a winner
- Check accepted tuple; delegate payload validation
- Check vocabulary membership only
- Route to the domain owner; report legality not evaluated
- Resolve within the selected recorded snapshot
- Exclude validTo; reject zero duration or overlap
- Return insufficient context, never false
- Choose the latest eligible commit; before first receipt return unknown
- Pin the returned sequence for stable historical content
- Append a corrected snapshot; compare historical answers
- Return unchanged root only for exact authorized replay
- Reject stale writes; host records conflict without altering history
- Require current grant; preserve old attribution
- Deny before hidden ledger/query diagnostics
- Report truth and transition legality as unevaluated
- Freeze new writes; retain historical reads
- Admit at local receipt; require actual host receipt for new admissions; static imports cannot prove receipt history
- Reject unsupported input; do not silently truncate
- Install own companion identity and validate nested snapshot
- Allow same-version roundtrip; refuse unsupported migration
Hazards and failure modes required Filled
- Retroactive edits that change past reports.
- Overlapping validity making two values current at once.
Standards and interfaces required Filled
- SQL:2011 temporal tables.
- RFC 3339 timestamps.
Context of use required Filled
- Any company fact that changes over time and is reported on later.
Sources Filled
- Research record EM-XCT-04: independent provider studies, audits and reconciled findings - Evidence behind the release; claims in the card trace to it.
- Enterprise Temporal History 0.1.0 specification - Normative release, digest sha256:5f68da29bf40481f2303dffa8f4f48aaa051b24d35b57405d2a0b7da7b6817f7
Open questions
- Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits.
Machine files
Provenance
enterprise research · reviewable-draft
Built from: models/enterprise-temporal-history/versions/0.1.0/spec.json, models/enterprise-temporal-history/catalogue-entry.json, ver-cy/world-models/card-supplements/enterprise-temporal-history.json