WEBVTT

1
00:00:00.140 --> 00:00:03.762
Your agent has permission.
Its pricing is out of date.

2
00:00:03.762 --> 00:00:07.042
Here’s the check I would make
before it sends that quote.

3
00:00:07.042 --> 00:00:09.745
Imagine a customer asks
for updated pricing.

4
00:00:09.745 --> 00:00:13.738
The agent can access the CRM, draft
the quote, and send the email.

5
00:00:13.738 --> 00:00:15.831
All three permissions are valid.

6
00:00:15.831 --> 00:00:18.566
But the price sheet it
used expired yesterday.

7
00:00:18.566 --> 00:00:21.825
That’s the problem behind
Permission Is Not Proof.

8
00:00:21.825 --> 00:00:23.964
First, make the evidence visible.

9
00:00:23.964 --> 00:00:27.172
Which price sheet supports this quote?

10
00:00:27.172 --> 00:00:28.731
Who issued it? When was it valid?

11
00:00:28.731 --> 00:00:33.353
If it’s stale, missing, or contradicted,
pause the consequential action

12
00:00:33.353 --> 00:00:37.217
and resolve the gap. Second, bind
approval to the specific decision.

13
00:00:37.217 --> 00:00:41.276
The person reviewing the quote needs
the evidence, uncertainty, recipient,

14
00:00:41.276 --> 00:00:43.464
attachment, and proposed terms.

15
00:00:43.464 --> 00:00:48.260
An approval should cover that package
within a defined scope and time window.

16
00:00:48.260 --> 00:00:52.071
Now watch what changes. If the agent
edits the amount, swaps the attachment,

17
00:00:52.071 --> 00:00:56.476
or changes the recipient after approval,
the earlier approval may no longer

18
00:00:56.476 --> 00:01:00.541
apply. Our proposed contract requires
the action to be checked again before

19
00:01:00.541 --> 00:01:04.326
execution. We call the reviewable
record a Governed Decision Object.

20
00:01:04.326 --> 00:01:08.693
Think of it as the decision, its
supporting evidence, its authority, and

21
00:01:08.693 --> 00:01:12.199
the exact intended action, kept together.

22
00:01:12.199 --> 00:01:15.841
Third, prove the effect. A successful
tool response is useful evidence,

23
00:01:15.841 --> 00:01:19.667
but the receiving system needs to
confirm what actually happened.

24
00:01:19.667 --> 00:01:23.539
Record the source-native receipt
and read back the relevant state.

25
00:01:23.539 --> 00:01:26.622
If completion is uncertain,
reconcile before retrying.

26
00:01:26.622 --> 00:01:29.279
Don’t turn a timeout
into a duplicate send.

27
00:01:29.279 --> 00:01:33.393
The paper’s appendix makes these
boundaries concrete with an illustrative

28
00:01:33.393 --> 00:01:35.721
decision object and six failure cases.

29
00:01:35.721 --> 00:01:39.558
Expired evidence, changed recipients,
revoked authority, and missing receipts

30
00:01:39.558 --> 00:01:42.046
each have a defined expected response.

31
00:01:42.046 --> 00:01:44.400
Those are proposed acceptance criteria.

32
00:01:44.400 --> 00:01:47.267
They are not executed
tests or production proof.

33
00:01:47.267 --> 00:01:52.044
This is the direction behind Whitewater
AIOS: connecting decisions, evidence,

34
00:01:52.044 --> 00:01:55.541
authority, action, and receipts
across the AI tools you use.

35
00:01:55.541 --> 00:01:58.511
LLM-agnostic. Model-agnostic.
Agent-agnostic.

36
00:01:58.511 --> 00:02:02.726
The human belongs inside that decision
process, with enough context to

37
00:02:02.726 --> 00:02:05.348
challenge, approve,
narrow, or stop the action.

38
00:02:05.348 --> 00:02:08.372
Human decision integrity
has to survive delegation.

39
00:02:08.372 --> 00:02:13.415
Here’s the practical rule: before an
agent acts, make the decision reviewable.

40
00:02:13.415 --> 00:02:15.734
After it acts, verify the effect.

41
00:02:15.734 --> 00:02:19.604
Read Permission Is Not Proof in the
PDF attached to my LinkedIn post.

42
00:02:19.604 --> 00:02:22.221
The compact technical
appendix is included.

43
00:02:22.221 --> 00:02:25.500
Keep the decision visible.
Bring back the receipt.