gauntletlisted

# Gauntlet — Run the System Through Its Trials A diner orders, pays, eats, and leaves satisfied. That is the surface — the real user experience, the happy path. Gauntlet's job is what happens *underneath*: the moment the diner pays, you slip behind the counter and sweep-test the entire payment machine — not "did this one card charge," but every branch of it (decline, double-tap, refund, partial, wrong currency, retry), under volume, all entered from the **exact real state the order left the system in.** So gauntlet runs two layers at once. A realistic **user journey is the spine** — it decides which subsystems get hit, in what order, and from what un-mocked state. And at each action, a **deep sweep of the real subsystem behind it** — proving the machinery is sound, not just that the click worked. The diner leaving satisfied means *both*: the journey completed for them, and every station their actions touched came back clean. It is the action-twin of the family's study skills. `devour` maps a codebase to understand it; `bedrock` runs code to ground a claim in reality; **gauntlet drives a whole stateful system's lifecycle as god and user at once, then adversarially verifies the truth it computes.** It borrows `devour`'s discovery to find the levers and `scour`'s "falsify, don't confirm" stance to pull the trigger. Lineage, so it isn't hand-waving: a fusion of **deterministic simulation testing** (FoundationDB/Antithesis — drive the world, assert invariants), **agent-based p