# Adoption limits

Reviewable draft; one single-valued scope and one host sequencer. No real-organization validation, distributed consistency, engine adapter, fine-grained disclosure, IAM, payload validation, transition engine, signatures, clock attestation, durable conflicts, erasure or existing-Dimension migration. Full snapshots have structural limits, not an enterprise throughput claim. Before production, implement durable serialized storage, scope uniqueness, authentication and current rights, a reliable clock, conflict audit, strict input parser/budgets and locally required retention/disposal. Historical source times never establish earlier local knowledge. Parent source/profile holds remain in crosswalk.json.

At capacity, even a new archive commit may be refused; use host policy to freeze writes and plan migration before exhaustion. The host owns global native fact-ID uniqueness. The nested validator checks only the immediate predecessor ID and assumes native envelope checks were already performed.

The inner recorded axis belongs to the timeline host, not to the native Dimension storage log. A pre-existing trusted host timeline can be installed later; synthetic January/February receipts in acceptance do not assert that the newly created Dimension existed then. Clock authenticity and history authenticity remain host obligations. A mistakenly admitted forward receipt can disable all reads and writes until catch-up. Before admission, enforce a clock-skew guard against a trusted reference. If it fails, quarantine/freeze and preserve the original evidence; recovery needs verified catch-up with current policy or an explicitly governed new timeline identity with provenance and disclosed continuity loss. No in-place repair or automatic recovery is implemented.