IDENTITY BOUNDARY / V1
Cross into your private workspace.
Google or GitHub establishes identity. The workspace preserves private context. Neither becomes release authority.
public field→
identity→
private workspace
Restoring the private session…
CONFIGURATION BOUNDARY
Identity infrastructure is ready for provider configuration.
No simulated sign-in is available. Google and GitHub will activate only after the production Supabase project is configured.
AUTH ERROR
The identity boundary did not open.
Choose a provider and try again. No private workspace data was exposed.
01 / CHOOSE IDENTITY
One quiet boundary. Two verified providers.
Continue with the provider you trust. SemeAI stores an internal identity distinct from the external account.
01 / SEMEAI IDENTITY
Private identity active.
PRIVATE SESSION- Primary email
- —
- Created
- —
- Connected identities
- —