Seeded pre-pilot demo data: all Q2 and June–July records on authenticated screens are illustrative operational fixtures, not live participant records. The public pilot remains scheduled for 1 September–30 November 2026.

/manage · Sprint 7 · 13–24 July 2026

Hello Marcus

This is the shared entry point to the admin area. You are seeing the work that belongs to the system admin role — account lifecycle, cooldown status, infrastructure and the guard rail audit. Areas owned by other roles are still listed so you can see where the queue is stuck, but you have no controls inside them.

Active accounts

of 96 registered

In cooldown

seven-day break from the betting floor

Data export or deletion requests

earliest deadline: 31 July

Safety checks

14/14

sprint 6 · pass · signed off

Counts are rebuilt at 06:00 each day.

Your work today

⏳

1 account-suspension request waiting on a second approver You raised it, so under the two-person rule you cannot approve your own. Valid cooldowns have no early-release request path.

Open

🗑️

3 data deletion requests still open U-10188 · U-10412 · U-10466 · earliest deadline 31 July

Work the queue Cooldown status

🛡️

Sprint 7 safety checklist has not been run Run it before the release branch is merged

Run

System health

Component	Status	Note
Odds data feed	Running	Synced 06:00 today. Read-only — there is no adjustable parameter.
Push notification service	Running	Learning reminders only, never betting reminders.
Database backup	Running	Last run 03:00, encrypted.
Content review queue	4 waiting	Not yours to action — shown so you can see where the queue sits.
Risk facts missing a source	2 items	Blocked in the data layer, so they cannot be published.

What this role cannot do

Cannot change odds — no screen, no setting, no "admin mode".
Cannot lift or shorten a valid cooldown. There is no early-release request path; assignment faults use the separate incident workflow.
Cannot read an AI companion transcript because the current outbound companion does not send or store conversation text in tibbi.
Cannot grant or top up tokens under any name — there is no grant, bonus or promo endpoint.
Cannot restore a lost Family asset for a player, even after a complaint — that capability was removed from the schema.

This is not a list of things not built yet. These functions do not exist in the code on purpose, so the rules outlive the people who wrote them.

Owned by other roles

You can see these areas but not act in them. Access follows the role, not seniority.

Learning videos, question bank, risk facts — content admin
Review queue for sensitive content — clinical reviewer
Pilot measurement and reporting — impact analyst
Sponsors and reward pools — sponsorship manager

⇄ Switch account