ENGINEERING INDEX / ENTRY 09
CASE 09 / AUTHORIZATION / REPLAY DEFENSE
Approval should work once.
A short approval action needs to authorize one named operation, not open a standing door. J-Bot mints signed action tokens for a specific action and record.
Source project: J-BotFocused tests passedReviewed September 25, 2026
How does a remote approval avoid becoming a reusable permission slip?
02 / THE SYSTEM
Where the handoffs happen.
Redemption burns the token. Replay, modified payloads, mismatched actions, expiry, and missing signing secrets are refused in focused tests.
- 01Mint scoped token
- 02Check signature and expiry
- 03Match intended action
- 04Redeem once
What the record earns.
One-use, expiry, tamper, action-scope, and missing-secret checks passed.
- Observed receipt
- On September 25, 2026, the action-token test file passed as part of a 49-test J-Bot safety batch. The tests exercise first use, replay, tampering, expiry, action mismatch, and fail-closed secret handling.
- Source and scope
- J-Bot jbot_core/security/action_tokens.py and tests/test_action_tokens.py; current checkout HEAD 9f94d83 with unrelated uncommitted work.
04 / THE LIMIT
What this does not prove.
This proves the token component under tests, not the security of every notification channel, deployment secret, or end-to-end approval path.
Where the work goes next.
Trace a redacted approval from delivered prompt through redemption and audit receipt on a pinned revision.