# Failure, retry, and reconciliation

Failure semantics are stated by phase so a policy result is not confused with delivery, execution, recording, or export.

- Canonical: https://5d.langoni.me/evidence/failure-and-retry/
- Evidence strength: Design target
- Evidence form: Interactive demonstration
- Version: 1.0.0
- Author: Loren Angoni; 5D product owner
- Created: 2026-09-27
- Updated: 2026-09-27
- Verified: 2026-09-27

## Scope

The phase vocabulary and retry disclosure implemented by the public website simulation.

## Separate the phases

Policy disposition, execution outcome, authoritative-record status, and optional export status answer different questions. A successful policy decision does not imply that the tool ran or that evidence was retained.

Unavailable or expired approval is not permission. Missing evidence, malformed observer output, duplicate delivery, and record failure remain explicit states.

## Retry owner

The integration owner decides when reconciliation is complete and whether another attempt is safe. Changed input, policy, configuration, or state may change a later result.

## Claim register

### Retries are new attempts

Evidence strength: Design target  
Evidence form: Interactive demonstration  
Evidence: website-action-flow

Each retry receives a new attempt identifier and is evaluated against the current normalized input, policy, configuration, and relevant state.

Limit: Re-evaluation is not evidence of idempotency or durable duplicate suppression.

### Unknown stays unknown

Evidence strength: Design target  
Evidence form: Interactive demonstration  
Evidence: website-action-flow, public-hooks-source

An unknown downstream outcome prevents the website scenario from claiming success and calls for reconciliation before a new side effect.

Limit: The website does not operate a production reconciliation service.

## Limits

- The page does not prove exactly-once execution, durable deduplication, or production reconciliation.
- The cited public source does not establish the behavior of every possible adapter or deployment.

## Sources

- [5D hooks implementation at public commit c22213b](https://github.com/theDoc001/fivedrisk/blob/c22213b513d4be167a0704244ad08c54e4ed1984/fivedrisk/hooks.py); immutable-public-source; commit c22213b513d4be167a0704244ad08c54e4ed1984; verified 2026-09-27
- [5D action-flow walkthrough](https://5d.langoni.me/action-flow/); website-artifact; website evidence 1.0.0; verified 2026-09-27

---
Illustrative website evidence only. No certification, legal conclusion, production integration, or complete coverage is represented.