Trust & operations
Wizard Gang Shark Tank is a browser game. A tank is one of its four game rooms — a single running world with its own players, its own leaderboard and its own log; the word is used that way everywhere on this site. These pages are the evidence behind the service that runs them: what it is doing right now, what it has done, what it costs, and where it falls short.
Everything published here is read from the running service at the moment the page is built. Each figure below links to the page that owns it — none of them is stored twice.
What is on each page
- Register
- Every ISO/IEC 27001 and 42001 control, what this service does about it, and the live route that proves it. A control may only be marked met when a reader can open that route.
- Policies
- The written record the two standards ask for — context and scope, risk method and assessment, the Statement of Applicability, and the rest — published as pages rather than filed as documents nobody can check.
- Operations
- Live availability, the incident record, the append-only control receipt chain, state copies and restore drills, and the delivery record.
- Evidence
- The 90-day service action log and the 24-hour per-tank capture logs, searchable and downloadable.
- Spend
- What the service consumes against each free allowance and against the hard limit that closes the game rather than billing.
- API
- Every route this Worker serves, including the unauthenticated ones and the limits on them.
The rule these pages are held to
A row marked met must name a live route that demonstrates it. Implemented but unrecorded is partial; nothing is silently a gap. An overstated register fails an audit faster than an honest one with open gaps, and it makes every other row suspect — so where this service is weaker than it would like to be, the page says so.