ASAdika SmithCloud app platform

Operations

Game save operations lab with live evidence

Operate on a per-viewer fake game-save sandbox with API-backed CRUD, dry-run evidence, execute, backup artifacts, and rollback.

IntermediateFirestoreAPI routesDry runBackupCSV evidenceRollback

Live operations lab

Game save operations control room

This lab uses a per-viewer sandbox. The page calls server-side API routes, the API changes fake Firestore game-save data, and every cleanup run leaves reviewable evidence.

Sandbox

Creating...

CLI handoff

Same sandbox, external operator tool

Creating sandbox command...
Working

Starting sandbox...

Firestore-backed records

Game saves

0 records

Run artifacts

Evidence trail

0 artifacts
No artifacts yet.Run DRY_RUN or Execute to create evidence.

CSV-style evidence

No run selected

No report selected.Backup artifacts store records; dry-run, execute, and rollback artifacts store report rows.

Why it matters

Safe automation is easier to trust when a reviewer can see the data, run the operation, inspect the evidence, and restore the backup.

Field notes

  • The browser never writes directly to Firestore; it goes through API routes with a sandbox token.
  • DRY_RUN creates the same decision rows the execute step will use.
  • Execute writes a backup artifact before removing duplicate, expired, or corrupted saves.
  • The evidence table shows why each save was kept, skipped, deleted, or restored.
  • The separate CLI repo can target the same sandbox so the website becomes the visual control room.