Credentials prototypes
Table of Contents
1. Summary
Passwords, sign-in state, and the audit of who signed in.
3 prototypes answer to this group. Each one is a static page under
doc/prototypes/, opens with no build and no session, and reads mock data
only. The table below opens each one and says what it argues. Where a
prototype carries a Gemini review, the last column opens it: a review is a
generated alternative kept beside the agreed design, never instead of it.
Prototypes is the top page and the only inventory.
2. The prototypes
| Prototype | What it argues | Open it | Review |
|---|---|---|---|
| Audit sign-ins | The tenant administrator reads who signed in, what failed, and where from, without leaving the tenant’s own area. | prototype | none |
| Protect my account | The member's security screen: the password and the sign-in state, with the variants disagreeing about where the save boundary sits. | prototype | none |
| Rescue access | The administrator's rescue access: diagnose first and then act, so the recovery link is the administrator's action and not a self-service one. | prototype | none |
3. Adding a prototype
Create doc/prototypes/credentials/<name>/ with an index.html, and a
prototype.css and prototype.js when it needs them. Open the page with
the links table every prototype carries, and leave its review row at
none. Add a row to the table above, with the design note beside the
prototype when there is one. Stop there: the site build finds every
prototype under this tree, so no build file names it.
A review goes at doc/prototypes/credentials/<name>/review/, with an
index.html that lists its screens. The row names it, and the
prototype's review row points at it. Prototypes states the
whole method and the rules that hold for every group.
4. See also
- Prototypes — the top page: the groups, and the one way to add a prototype.
- Credentials journeys — the journeys these prototypes answer.