Demo · Write-back
One agent is wrong
decide which trust signal is allowed to move
When an agent is wrong, the question is not how much to distrust the number. It is whether the number did anything wrong at all.
Master toggle
Attribution guard is on. The system attributes the failure before it charges a ledger.
Set the master toggle and the true cause, then resolve. The agent has already acted on Preliminary Revenue.
Captured at action time
The agent acted on Preliminary Revenue. This is the candidate set the system kept, the one it picked and the one it passed over.
Preliminary Revenue
picked · acted on
Final Revenue
passed over · 1 hop away · sibling
Hop-distance gate fires. A sibling sits one hop away, so the replay is worth paying for. Recall-first gate, replay supplies precision.
Where the loss is allowed to go
Preliminary Revenue
the number's shared trust
The agent
its reliability
Attribution decides which trust signal is allowed to move.
Downstream of Preliminary Revenue
Other agents and analysts reading this number correctly.
Lit. The guard kept the agent’s mistake off the number they share.
Consumers protected from the agent's mistake
0
The contrast
Run the wrong-grab with the guard on, and the agent takes the hit while the number stays clean. Flip the guard off and run it again, and the number craters for a mistake it never made.
The agent's mistake is the same in both runs. The only difference is whether attribution runs before the debit. Without it, one agent's error resets a number that everyone else read correctly, and the agent's own reliability stays falsely pristine.
Read the full article
The Write-Back Problem