docs
calendar
main
#64 / 100
docs(calendar): freeze Phase 1D Google read-only OAuth connector spec
Step 11a (Thinking) — freeze the Google Calendar read-only OAuth connector: confidential web client + PKCE (reuse companion-oauth-pkce), least-privilege read-only scopes, encrypted refresh-token vault (AES-256-GCM/scrypt pattern), connector API (POST/GET/DELETE + callback), incremental sync + 90d/365d horizon, 24h revoke-delete SLA, PII minimization, and the Knowtation seven-tier matrix. Build gated on CALENDAR_OAUTH_GOOGLE_AUTHORIZED (false). Build = step 11b (Auto).
Also resolves V0-spec open decisions (recurrence, horizon, timeline) and marks 1D spec FROZEN; updates OVERSEER-HANDOVER active track to 11b.
sha256:1f6224b3768b0f9391d618dc0cbe9ae64a09360a1dd657561b3192253a78b523
sha
sha256:2e674eaaac2e75b8a02e02efc3f45ce5729232603ba4053eb0e14e962784f348
snapshot
Older
Merge pull request #260 from aaronrene/muse-mirror
sha256:501b04b57c908401c603a621420614cb622a1b219bb85ba935e964794538ec44
All commits
Newer
mirror: muse 110205d..5cfa2db (Google OAuth connector Phase 1D, …
sha256:3f2b0219823fdee58964e51f9350bdbf35011f50bad699e29f8b8448e3a3ee58
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:1f6224b3768b0f9391d618dc0cbe9ae64a09360a1dd657561b3192253a78b523 --body "your comment"
No comments yet. Be the first to start the discussion.