ATTEMPT 01
FAILED CLOSED
Required evidence was not current enough for the bounded decision. No later success changes that fact.
PLATFORM · FAILURE & RECOVERY
A later pass does not erase the failure.
Causance treats failure as evidence. Rejected, stale, superseded and interrupted states remain part of the governed history so a later success can be understood without rewriting the path that produced it.
Bounded recovery, not magic rollback. Current product architecture includes recovery, replay, retained-history and reconstruction mechanics within exact implemented scope. This page does not claim universal recoverability, zero-loss recovery, provider failover, customer recovery performance, or an RTO/RPO/MTTR commitment.
PRESERVED HISTORY
Three attempts. Three different facts.
A successful successor establishes a later result. It does not make the earlier failure disappear, and it does not make the earlier authority or evidence valid in hindsight.
ATTEMPT 02
REJECTED
A corrected candidate existed, but the evidence or authority envelope did not match the required scope. The rejected state remains attributable.
ATTEMPT 03
VERIFIED
A later exact candidate satisfied the requirements that applied to that candidate. The later result sits beside the failures rather than overwriting them.
FAIL CLOSED
Uncertainty is a state, not an invitation to guess.
When required facts are missing, stale, conflicting, malformed, superseded or inapplicable, an implemented contract can require revalidation or block progression. The system does not need to convert uncertainty into a confident answer just because an actor is ready to continue.
Missing
A required source or evidence object is absent.
Stale
The evidence exists but no longer satisfies the freshness condition in scope.
Conflicting
Material sources disagree and the conflict remains visible until the owning authority resolves it.
Inapplicable
The evidence may be valid elsewhere but does not match the actor, operation, revision or condition being decided.
BOUNDED RECOVERY PATH
Recovery restores context. It does not invent authority.
A bounded recovery path preserves the evidence required to understand the failure, reconstructs supported state, and separates restoration from any new permission to act.
Make the failed, indeterminate or divergent state explicit.
Preserve the exact state instead of continuing on an assumption.
Retain failed attempts, source identity, evidence and decision context.
Rebuild or replay what is supported without reviving execution authority.
Re-evaluate the facts and requirements that now apply.
Later action uses separately governed authority where required by the lifecycle.
RECOVERY EVIDENCE
A recovery result proves the recovery actually exercised.
It should not silently become a claim about every environment, failure mode or customer condition.
SUPPORTED WITHIN EXACT EXERCISED SCOPE
- Failure state can remain append-preserved.
- Supported decision context can be replayed or reconstructed without creating authority.
- Recovery can require fresh evidence and separately governed authority before later action.
- A bounded exercise can support the procedure and environment actually exercised.
NOT IMPLIED
- Automatic retry or arbitrary execution re-run.
- Universal customer or production recovery.
- Zero-loss recovery or provider equivalence/failover.
- Guaranteed RTO, RPO, MTTR or continuous availability.
RECONSTRUCT THE DECISION