Your AI staff
Create AI staff and choose the connection they use. Each staff member has their own profile and permissions.
Checking your session…
🔒
Restricted page
The readiness registry is limited to superadmins and leadership. Your own AI staff and run records are available above.
Back to OfficeAI Agents
Every AI agent we run — what stage it is really at, who is accountable for it, and how far through the five readiness gates it is.
AI staff identity inventory
Explicit links only. Matching names do not create a link or grant access.
Loading inventory…
Identity baseline. Use AI staff management above for audited ownership and explicit links. Existing role and client settings continue to control access.
Registry
Live agents first. Click a row to see its five gates, its owners, and the code route it corresponds to.
| Agent | Stage | Owner | SOP owner | Route | Readiness |
|---|
No agents registered yet.
Every AI feature we run should have a row here, with a named owner.
Every AI feature we run should have a row here, with a named owner.
How readiness is scored.
The percentage is completed sub-items ÷ total sub-items across all five gates, computed on the server
(see
Route is a soft correlation to the
readinessPercent() in server/src/ai-agents.js) so this page never invents its own number.
A gate with a total of 0 is unscoped: it counts toward neither side of the fraction, and an agent with no gate
totals at all scores 0%, not 100% — an unscoped agent is not a ready agent.
Route is a soft correlation to the
route tag on the AI usage log,
not an enforced link — use it to line an agent up against its real spend on the AI Usage page.