Verified ownership and recovery
Email verification, secure local-account reset, and recovery controls must be designed together.
Identity architecture ยท foundation contract
One TIGUNNY identity. Explicit tenant authority.
The intended provider options resolve to a canonical person record. A successful sign-in establishes who the user is; it does not establish a tenant, role, or permission.
MicrosoftGoogleGitHubTIGUNNY local
CANONICALUser identity
SERVER GATETenant membership + role + permission
ALLOWDENY + AUDIT
Required before production
Provider choice is only one part of the identity system.
MFA and guarded linking
Linking a provider must require fresh proof and must not trust an email match alone.
Session control
Issuance, rotation, expiry, revocation, device visibility, and secure cookies need an approved operational model.
Auditable identity events
Sign-in, failure, verification, recovery, MFA, linking, session, and administrator actions require durable evidence.
Current truth
None of these providers is live.
This foundation defines the boundary and proves tenant authorization with an explicit local development identity. Provider selection, callbacks, secrets, policy updates, and production operations remain separate decisions.