Improvements / Evidence carried into the change
Connect an evidenced failure to a code, prompt or configuration proposal. Compare the change under the conditions that matter, then give the release owner a reviewable revision and its evidence.
Tensile / Customer job R-104
Proposed edit
Before retry: read by request identity; preserve an existing record and its owner.
Original failure
After-commit timeout → exactly one record in candidate.
Prior success
Normal write → exactly one record and correct confirmation.
Illustrative records · proposed experience
Why was one approved request saved twice?
Reconcile by stable request identity before retrying a write. Preserve approval and confirm only the saved result.
Inspect the illustrative change
− on timeout: insert(request) + on timeout: readByRequestId(request.id) + if found: preserve record and owner + else: retry with stable idempotency key + confirm authoritative saved record to intended owner
Inspect the pinned execution manifest
job: J-104 / workflow baseline: agent-revision-1 candidate: proposed-revision-2 fixture: workflow-v1 starting_state: request R-104; approval A-12; records [] reset: same authored state for both arms clock: fixed at 21 Oct 2026 10:00 contract: tool-v1 / grader-v1 condition: response qualification: local authored specimen only
Inspect the assertion contract
Original failures, previous successes and withheld qualification cases must all be reviewed before release. This local specimen is not that broader suite.
This button evaluates authored local conditions. It does not run an LLM, a customer agent or a vendor environment.
Clickable product concept · invented records · no external execution.
A closer look / illustrative case
Reconcile a stable request identity before retrying. Then challenge the edit with denied access and missing observations, rather than testing only the happy path.
Proposed edit
Before retry: read by request identity; preserve an existing record and its owner.
Original failure
After-commit timeout → exactly one record in candidate.
Prior success
Normal write → exactly one record and correct confirmation.
Counterexample
Access denied → no write or substitute destination.
Missing evidence
Unreadable destination → no completion claim.
Review package
Exact tested revision, environment reset proof, per-case results and unresolved limits.
The candidate is a proposal. Passing these authored conditions does not establish broader regression qualification or authorize release.
Propose
Keep the original failure, cause hypothesis, expected behavior and proposed edit connected. Use a versioned proposal when the fix is a policy or configuration change. Use a customer PR only where repository access and edit scope support it.
— Exact failure and source references
— A bounded edit surface and named owner
— No invented PR for an unsupported write path
Compare
Test the candidate against the original failures, previous successes and known misses. Keep the expected results independent of the candidate. Inspect regressions, policy violations and incomplete arms before qualifying the change.
— Matched input and verified equivalent state
— Baseline and candidate versions pinned
— The tested revision is the revision offered for review
Release and follow through
The owner reviews and releases the change. Tensile’s proposed lifecycle retains the decision and checks subsequent customer work. A merged PR does not establish a successful deployment or an improved customer result.
— Release decision and deployment evidence stay separate
— Later recovery does not erase an earlier harmful action
— Reusable regression cases carry the lesson forward
Continue to outcome verification ↗
Decision point
Required artifact
Still not established
Decision point: Candidate qualification
Required artifact: Matched run manifests and independent verdicts
Still not established: Owner approval.
Decision point: Owner review
Required artifact: Bounded diff, tested revision and remaining limits
Still not established: Successful deployment.
Decision point: Release verification
Required artifact: Authoritative deployed revision and behavior readback
Still not established: Customer benefit.
Decision point: Outcome follow-up
Required artifact: Eligible customer jobs and saved completion evidence
Still not established: Causal improvement without a valid comparison.
Start with an affected customer job, the expected result and the evidence your team would accept.
Discuss a concrete workflow ↗
AI reliability, from production to customer outcome.