A device MUST hold a hash of what the browser says it is; a session MUST say who is signed in, to which tenant, from which device, how sure it is of who it is for (assurance level), how it was authenticated, when it ends if unused and when whatever, and why it was ended early; a refresh token MUST hold a hash, be unique, belong to a family of tokens rotated from one issue, and say which token replaced it, so that a reuse can end the family and the session.
Enforced (check): .github: cd commons/data && bun run verify — suite/identity.test.ts: no concept of any module holds a secret, a prompt or raw arguments in the clear, every concept that holds a secret is restricted, and an agent's provenance and its calls are kept as pinned versions and hashes; suite/identity.test.ts: the identity model's uniques are in the database: one login in a tenant, one name for a group in a tenant, one passkey credential id, one hash for a refresh token, one verified domain, one membership of a user in a tenant
Proved by: data/suite/identity.test.ts
Written in: data/models/identity/concepts.ts
Tests: passed: suite/identity.test.ts the identity model's uniques are in the database: one login in a tenant, one name for a gr; passed: suite/identity.test.ts no concept of any module holds a secret, a prompt or raw arguments in the clear, every con