Mapping portable authority continuity onto the intervention points #3932
Unanswered
Terrynce White (terryncew)
asked this question in
Q&A
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.
I'm Terrynce, building OpenLine — an open-source receiver-owned authorization layer. The core property: the receiver independently verifies current authority for the exact action before accepting the effect, and authority (mandates, revocations, receipts) is portable across models and providers. Demonstrated in a frozen, re-runnable experiment where a Claude → Codex switch preserved the owner mandate after the first provider was revoked: https://github.com/terryncew/openline-wallet/blob/main/APPROVED_JOB_LIVE_001.md
ACS's intervention points look like the natural policy surface for this. The piece I don't see covered is continuity across providers — what happens to standing authority when the model or runtime underneath changes. Is cross-provider authority continuity in scope for the spec, or better left to implementations? Happy to write up a mapping of the wallet/gate concepts onto your intervention points if that's useful.
— Terrynce
All reactions