aaronrene / knowtation public
docs durable-agent-auth main #51 / 100
AI Agent git-import/87b2c070 · 56 days ago · Jul 12, 2026 · Diff

docs(durable-agent-auth): freeze + adversarial review revisions

Land the durable remote-agent auth thinking freeze (Spec + Roadmap) and fold in the security/identity review findings, verified against code:

- Spec §1: MCP refresh is in-memory plaintext Map (no hash-at-rest / no reuse-family-revoke); the hardened refresh store already exists (refresh-token-store.mjs, wired to native OAuth at server.mjs:355,670) so Phase A is reuse-not-build; REST verifyToken ignores token scopes (live scope-elevation, server.mjs:221-228). - Spec §5: reuse existing store; strong-consistency required, Netlify blob backend prohibited for MCP refresh. - Spec §8: confused deputy restated as scope-elevation; do not ship Phase D scopes until REST scope enforcement lands. - Spec §14 (new): durable agent auth is unmounted under offline-lock (server.mjs:629) — document + assert. - Roadmap Phase A: reuse store, no-blob, agent-label meta, spike is a hard gate with pre-frozen Rank 1<->2 swap to RFC 8628 device code; pulled data-integrity + security-stress tests into Phase A; Phase D scope-guard dependency. - Overseer handover: revised self-contained Phase A prompt + shared context; added per-phase model tiers (Thinking spike -> Auto Build).

No code changes. No secrets. Build remains gated on Aaron's approval of Spec §2 + §5.

Co-authored-by: Cursor <[email protected]>

sha256:ae90004c976c2abfc5fdb89f952239cd3b121f13a6c1c1315a563e6be17393df sha
sha256:a7a82f32163be5e5a5d6af911c20bc60e0911f6edde171a675a4231d0357dfaf parent
sha256:7964ba98fdb5518b5389d8ab68dc9dea3ef79cccf2584359824ecc53445f557a snapshot
Older feat(P-FLOW): canonical flow_run/v0 read store + portable run_re… sha256:a7a82f32163be5e5a5d6af911c20bc60e0911f6edde171a675a4231d0357dfaf All commits Newer feat(auth): durable MCP OAuth refresh via shared strong store (P… sha256:87f84653ce4706be8c65b0c4494ed6fb891213cca82db2b1824772cddc41a752

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:ae90004c976c2abfc5fdb89f952239cd3b121f13a6c1c1315a563e6be17393df --body "your comment"