SharkTank

It starts with multiplayer gameplay.

Players control sharks in a shared tank. They eat food, dash forward, fire rockets, and compete for score while the server keeps everyone in the same match. The security and operating features support that game; they are not the game itself.

A live game uses real resources.

Shark Tank is a game first, but running it creates real responsibilities. Multiplayer actions use billable cloud resources, public input must be checked, changes must be tested, and the fully AI-generated code needs a clear management process. Those controls must protect the game without getting in the player's way.

Shark Tank therefore includes the checks needed to run the game responsibly. They protect public input, control operator access, track billable activity, record changes, and provide a recovery path.

Secure operation is built into the game.

ISO/IEC 27001 provides principles for managing information security. Shark Tank applies those principles to every feature and to the way the live service is operated: access is controlled, input is checked, changes are tested, backups are verified, and important actions leave records. These are everyday safeguards, not a claim that a security incident has occurred.

• Public input is checked before the game accepts it
• Operator controls are protected and leave a record when they are used
• Each release records what changed and how the result was checked
• Daily backups are tested by restoring and reading the saved copy
• The service reports its current status and calculates uptime from its own records
• The service counts billable activity and stops costly actions at a hard limit

The AI story is how the game was developed.

ISO/IEC 42001 applies here because the codebase was developed entirely with AI-generated code. It guides how that development is managed: what AI is used for, how its output is checked, who remains responsible, and what evidence is kept.

• The application code is 100% AI-generated
• Policies describe how AI-produced changes are planned, checked, tested, and released
• Security, cost, accessibility, recovery, and evidence requirements apply to AI-produced features
• Tests and live records check the result instead of trusting generated code because it looks correct
• Jacob owns the service, approves its operation, and remains responsible for its results

Controls help the owner run the service.

Jacob operates Shark Tank. If a real incident occurs, he reports it, investigates it, resolves it, and closes the record. Built-in checks and status pages help him see what the service is doing and respond when action is needed.

Uptime comes from the service record.

The site calculates availability from the records kept since the project started. When those records support it, the page says 100% uptime maintained. If the record changes, the displayed number changes too.

Gameplay has a spending limit.

Joining a tank, running a live room, steering, dashing, and saving records all use metered cloud resources. The service measures that activity while the game runs. At the hard spending limit, it pauses gameplay and other actions that could add cost. Status, evidence, and recovery pages remain available so Jacob can review the situation before restarting normal play.

The rules and their results stay together.

Shark Tank documents its policies against ISO/IEC 27001 and ISO/IEC 42001. The same service keeps evidence for the controls it operates, including changes, uptime, billable activity, operator actions, backups, and recovery checks. This makes it possible to compare a written policy with what the game actually did.

More people can use the site and its controls.

WCAG 2.0 AA is a common set of web-accessibility rules. Shark Tank's public pages, menus, settings, and supported game controls are tested against those rules. This does not mean every visual action in the game has a matching nonvisual version; the claim covers the listed screens and controls.

• Public pages and supported game controls can be used with a keyboard
• Visible focus shows where the user is, while clear headings, labels, and skip links make pages easier to navigate
• Screen readers announce status changes and errors without moving the user's place
• Text and layouts remain readable with browser zoom and stronger contrast
• Options include reduced motion, larger text, color labels, captions, and steering help

Each service has one job.

The browser shows the game and public records. The Worker checks requests and serves those pages. Durable Objects keep live matches, logs, and operator records. R2 stores separate backup copies for recovery tests.

A game first, with its controls built in.

Shark Tank is a playable multiplayer game built entirely with AI-generated code. It runs with ISO-aligned security and operating practices, limits its billable activity, documents its policies, and maintains evidence from the live service. It demonstrates alignment; it does not claim certification.