You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9b2e45e
Browse filesBrowse the repository at this point in the historyBrowse files
docs: say that Orbit is a sign-in provider, and that its own door is Google
Plan 008 was recorded only in the plan and the ledger. Nothing a reader
consults to learn what Orbit is or what it serves mentioned it: not the
README, not the screen map, not the identity contract's endpoint surface.
The check turned up an older miss of the same kind. Living documents still
told people to sign in with GitHub, two days after the door moved to Google
on 10 August — README's stack list, AGENTS.md, SECURITY.md's threat surface
and two places in the product constitution. Those are current-state claims,
so they are corrected. Historical decision records are left alone, including
the ledger entry that locked GitHub at the time.
V6_IDENTITY_DATA_API.md is updated the way it was built to age: it declares
itself a design record with a "known divergences" list, so both the Google
move and the OIDC provider go there rather than being retrofitted into the
sections they contradict. The entry names those contradictions explicitly,
because section 1 still calls Google OAuth out of scope and section 2 lists
it as a non-goal.
The consent screen is added to the screen map as what it is — a surface the
worker renders itself, self-contained on purpose, and for many users the
only part of Orbit they will ever see.
Plan 008 is marked complete, with the limit of revoking written into the
plan itself so nobody reads "revoke" as "signed out everywhere".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments