Skip to main content

Failure envelope

Agent and tool boundaries normalize failures into safe structured data rather than passing provider bodies downstream.
Credentials, prompts, transcripts, drafts, private provider payloads, and stack traces are excluded from operator and model-facing envelopes.

Classification and action

Recovery sequence

Retries reuse stable operation and idempotency identities. They do not manufacture a new action or bypass human approval.

Effect recovery states

Only the explicit Prove duplicate suppression control creates replay evidence. Ordinary duplicate delivery suppresses the provider call without creating a new replay record.
A visible failure is a valid terminal outcome. Harmonia never converts an unavailable provider, missing credential, unverifiable effect, or exhausted retry into simulated success.
See Approvals & Audit for claim-before-effect ordering and Authenticated vertical-slice evidence for proof requirements.
Last modified on August 25, 2026