ZEVR
Admin
Start at Today. Every screen checks your permissions on the server, so a link here only means the screen exists, not that you can act on it.
- TodayOverdue work, deadlines, decisions due, new evidence and stale readings, each with its reason.
- MarketWhat is worth watching, on its own dimensions. Not a ranking.
- Demand & DiscoverySearch and AI visibility sources, explainable content opportunities, Visibility Lab.
- CommercialWhat ZEVR is prepared to offer, and what it is currently allowed to do about it.
- TalentApplications and decisions.
- ProductionCreator project queue.
- CompetitionEvents, matches, results and certification.
- RostersTeams, rosters, member moves and snapshots.
- PeopleEveryone with an account.
- Launch readinessGate states and the programs they block. Read only.
- ActivityThe audit trail.
- Projection healthOutbox and dead letters.
- Creator Ops (demo)Demo store and mock analysis. Not live data.
Operator tools
These act. They do not navigate.
Each one is authorized on the server and written to the audit trail. Several are destructive, and several require a second approver who is not you.
Session
Local probes — development only
Blocked outside local/test environments.
Person profile (read_any)
Account tier (privileged + dual approval)
Account status (lock / disable / re-enable)
Org OS offboarding (SOT §30 — disable + revoke)
Membership status (staff + dual approval)
Revoke session (revoke_any)
Audit trail (audit.record.read)
Ops verify-controls (R-01)
CMS refuse drills (handoff §8 / SOT §29)
Expected: HTTP 403 with distinct reason_codes. These edges exist so CMS cannot pretend to own later-batch domains.