crAppstore / Hercules Tests
Reliability needs scars.
Hercules Tests is a local-first gauntlet for proving that an app behaves under failure, recovery, scale, hostile input and restart—not merely on the happy path.
The fifteen labors
The sequence covers identity, repeatability, time budgets, malformed input, cleanup, event bursts, interruption recovery, containment, intent preservation, duplicate detection, redaction, defect detection, volume, cold restart and final evidence completeness.
The ratchet
Later tiers stay locked until every labor in the preceding tier passes. A failed rerun replaces confidence with a visible failure; proof cannot silently remain green.
Known-bug proof
The harness includes a deliberate defect switch. Turn it on and Labor 12 must fail. Turn it off and rerun. This proves the gauntlet can detect a known defect instead of awarding itself a ceremonial green check.
Persistence and privacy
Project fields, evidence and the ratchet live in this browser's local storage. Cold restart reloads that state. Exported JSON redacts secret-like tokens. Nothing is uploaded and no command supplied in the target field is executed.
Limits
This crApp demonstrates the blueprint's operating model with deterministic browser-side assertions. It does not replace project-specific unit, integration, security or deployment tests. Its job is to force an inspectable evidence trail and expose unproved assumptions.