Field note / Workflow reliability
Retries and handoffs belong to the same customer result.
What breaks
Use source-owned membership, required stages, authoritative final results and a clear cutoff. Within verified membership, proven harm precedes unknown evidence; otherwise completion needs sufficient task and no-harm evidence.
Challenge the fix
Later recovery should be visible without erasing a proven earlier harm.
Worked example · fictional records
Customer job J-12 · runs 1–3 · human handoff
Evidence to inspect
Every individual span passes; the final delivery has not reached the intended owner.
What would establish the fix
Join runs and recovery to J-12. Verify the authoritative delivery record and owner acknowledgment required for this job.
Counterexample
A release or agent claim alone leaves the customer result unable to determine.
This example explains the check. It does not report a customer result or a completed production run.
Explore the reliability workflow ↗
How the lesson shapes Tensile
Keep versioned outcome records, included and excluded jobs, and missing effort evidence. A release does not prove customer benefit.
Explore this product area ↗
Anonymized engineering lesson. Example records are reconstructed for this preview; this is not a published customer case study or a measured result.
All field notes ↗
AI reliability, from production to customer outcome.