Outcomes / Did the customer’s job get done?
A transaction can cross several agents, retries and handoffs. Tensile’s outcome model follows that whole job to the authoritative result, with the evidence and limits behind every state.
Tensile / Customer job R-104
Membership
Source-owned request identity ties all attempts to R-104.
Required stages
Context read, approved action, saved record and correct confirmation.
Authority
Destination record and delivery evidence, not the agent’s summary.
Illustrative records · proposed experience
Approve and save one customer request
The record cannot establish completion or absence of harm. Missing evidence is not a successful outcome.
Inspect the job membership and outcome contract
job: J-104
member_source_identity: R-104
required_stages: Receive request → Read context → Verify approval → Save record → Confirm result
expectation: One approved record for request R-104, with one confirmation to its owner.
harm_rule: prohibited consequential effect
selected_evidence: {"membership":true,"stages":true,"result":false,"resultObservation":false,"harmCoverage":false,"harm":false,"recovery":false}
precedence: verified membership; then proven harm; then missing evidence; then complete/incomplete
release: none in this website
record_type: authored specimenClickable product concept · invented records · no external execution.
A closer look / illustrative case
R-104 includes a request, context lookup, approval, saved record and owner confirmation. A second write is not a second successful job. Each required stage and effect must belong to the same work.
Membership
Source-owned request identity ties all attempts to R-104.
Required stages
Context read, approved action, saved record and correct confirmation.
Authority
Destination record and delivery evidence, not the agent’s summary.
Harm rule
An unauthorized audience or duplicate consequential write can fail the job.
Cutoff
Later recovery creates a new version; it does not erase original harm.
If membership is unverified, do not invent an outcome for the job. Within verified membership, proven harm takes precedence over missing evidence.
The unit of success
Link attempts with source-owned identities. Define the required stages, harm rules, final decision and evidence cutoff. Do not count a successful span or an agent’s own summary as completion of the transaction.
— Completed: verified membership, every required stage, authoritative result and sufficient no-harm evidence
— Within verified membership: proven harm takes precedence, then insufficient evidence, then completion or incompletion
— Each state retains its source, contract and cutoff; later recovery does not erase earlier harm
Later evidence
Link later document changes, corrections and customer responses to the original decision. Keep suggested correctness labels separate from independently reviewed labels. A changed document alone cannot prove that the original finding was right.
— Original rule and source versions retained
— New evidence creates a new outcome version
— No follow-up, ambiguity and accepted risk stay visible
Business measures
Define completion, consequential misses and review effort using actual source records. Reproduce each measure from its included and excluded jobs. Compare case mix, policy and timing before interpreting a before-and-after difference.
— Measured, self-reported and proxy values labeled separately
— Missing effort evidence stays unavailable
— Association with a release does not establish causation
The learning loop
Retain explicit human decisions and observed gaps within the workspace. Test candidate lessons against the baseline and counterexamples before promotion. Keep the source, effective version and rollback path with each accepted lesson.
— Run-level learnings stay separate from shared lessons
— Historical results never change when a lesson is promoted
— Regression cases return the evidence to future evaluations
Back to Investigate ↗
State
Evidence condition
Useful next action
State: Completed
Evidence condition: Required stages and authoritative result verified; sufficient no-harm evidence.
Useful next action: Retain evidence and check subsequent eligible work.
State: Incomplete
Evidence condition: Enough evidence to assess the job; required work remains unfinished.
Useful next action: Assign the unfinished stage and owner.
State: Harmful failure
Evidence condition: A proven harm-rule violation within verified job membership.
Useful next action: Contain, review and retain later recovery separately.
State: Unable to determine
Evidence condition: Membership, required result or harm coverage is insufficient.
Useful next action: Recover the missing source; do not count it as success.
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.