SUMMARY: Provisional permanence appears when a temporary status survives its evidence, deadline, or original purpose. What began as a pending judgment becomes the durable record that connected systems continue to trust.
Temporary states are necessary. A payment can be pending, an identity can require review, access can be briefly restricted, and a record can remain unverified while evidence arrives. The danger is not the temporary state itself. The danger is a system that knows how to assign the state but has no equally reliable way to end it.
A Deadline Is Not an Expiration Mechanism
A policy may say that a restriction lasts 24 hours, but the database field can persist indefinitely. A review queue can close while downstream copies remain unchanged. A human can reverse the original decision while cached interfaces, exports, and partner systems continue showing the old condition.
Decision half-life describes how corrections lose value after consequences spread. Provisional permanence describes the related storage failure: the disputed state remains available for reuse after the reason for keeping it has disappeared.
Copying Removes the Question Mark
The first system may understand that a status is tentative. The second system may receive only the label. By the third transfer, the timestamp, confidence, evidence class, and review condition can be gone. A provisional signal has become an apparently settled fact.
This is where data lineage becomes operational. A copied status should carry its source, assigned time, expiration time, authority, and current review state. Without that context, every recipient must guess whether the record is still fit for use.
Permanence Favors the Original Decision
Systems often require evidence to remove a restriction but require no evidence to retain it. This asymmetry makes inaction look safe. The old state persists because deletion, correction, and propagation each need an owner, while simple retention happens automatically.
An effective decision pause prevents immediate harm while review is active. It should also define what happens when the review clock ends. A pause without an expiration rule can become an indefinite denial wearing temporary language.
Test the Exit, Not the Label
For every provisional status, ask four questions: what event ends it, which system owns that event, where copies must be corrected, and what safe state appears when evidence never arrives. If any answer is missing, the temporary state is already designed for permanence.
Field assessment: a status is not truly provisional unless expiration is executable across every system that can act on it.
Continue the discussion in the Clandestinia forum.