Repository navigation
AI Execution Governance, Part 9: Revocation Complete Is a Conclusion, Not a Status Field #91
rain6fish
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A side-effect row reads
revoke_status = revoked. On the screen it becomes a green badge that says revoked.Those three words are not a field value. They are a conclusion, and a conclusion is supposed to be argued: did the compensation actually run, did the target actually return to its previous state, did the other system actually answer.
One sentence: "revocation complete" is at least three claims, and folding them into one boolean replaces three unperformed checks with a badge.
If that is enough, the rest is a table and three limits.
1. Completion is three things, not one
The three carry different evidence from different sources. Folding them into one boolean folds away which one is still missing.
2. What we return
Our restore check returns three values:
Two details matter.
First,
compensatingisunknown, not "not revoked". It covers both "compensation is still running" and "it never started". Neither state knows the outcome, and writing either one down would be a claim.Second, the boolean view's
falsemeans unproven. We also expose a boolean, and it returnsfalseforunknownas well. The comment on it says plainly thatfalsemeans not proven restored, not known not revoked. Callers have to go back and read the three-valued state rather than treat the boolean as the answer.On the outside we have two words as well: possibly not delivered, and delivered, no answer. That second one is the absence of a conclusion, and we do not relabel it as completion.
3. Why two values are not enough
Both ways of collapsing are wrong.
The middle value is not cautious wording. It is the only value that does not lie. A system with only two states will eventually assert something it does not know, on the first external timeout it meets.
4. A conclusion has to be refutable
A badge that says revoked counts as evidence only if some observation could overturn it. We give the conclusion a refutation path.
5. Four checks you can run
unknown, it will lie on some timeout.falsemean, refuted or unproven? Mixing the two is the dangerous part.Closing
Back to the badge. It should stand for three claims holding at once, not for three fields happening to line up.
"Revocation complete" is not a status field. It is a conclusion that has to be argued, and when the argument cannot be made the right answer is
unknown, not green.The mechanism above is taken from KeelBase, an open-source runtime that sits between an AI agent and a business system, re-checks identity, authorization, scope, risk and confirmation state before a tool runs, and writes every decision into a record that can be verified offline. The three-valued check is a way of reading here, not a shipped feature; KeelBase is its implementation and evidence carrier.
Repository: https://github.com/rain6fish/KeelBase
Three things stated plainly. The outside's "delivered, no answer" is a design value we have not tested end to end, so we cannot claim it was verified against a real external system. The declared-versus-held difference triggers only on the retry path that hits the idempotency key, because a first write has nothing to compare against. And the three-valued check is a reading of the code, without a bypass experiment.
Drafted with an AI assistant. The system, the positions and the mistakes are mine.
All reactions