RoarCAD

Reproducible evidence · checked August 31, 2026

What RoarCAD proves—and what it does not

Each claim belongs to a separate evidence lane. Source code, automated tests, deployment status, browser execution, and physical hardware are not interchangeable.

ClaimEvidenceReproduce
Agent preview cannot create a revisionWebMCP exposes four tools and no apply tool; domain tests assert stored state is unchanged until manual apply.bun test tests/webmcp.test.ts tests/domain.test.ts
Checkpoint integrity and ancestry are enforcedTests cover round-trip, size, tampering, unrelated projects, fast-forward, behind, and divergence behavior.bun test tests/checkpoints.test.ts
Manufacturing remains human-controlledClient and server validation reject unready designs; download and quote actions require visible UI controls.bun test tests/manufacturing.test.ts tests/eda.test.ts
Tool contracts and evaluation cases are checkedDeterministic tests enforce output limits and safety boundaries. Ten natural-language cases specify selection, arguments, sequencing, pagination, and no-call behavior; checking the case file does not measure an AI model's selection accuracy.bun test tests/webmcp.test.ts and bun run eval:webmcp; see the dated browser records for live execution.
PocketRoar's modeled slice is digitally cleanThe recorded revision generated 2,566 Circuit JSON elements with zero compiler and checker errors.bun test tests/eda.test.ts and inspect the tracked project evidence
The web application buildsTypeScript, Biome, Bun tests, and the Vite production build are required release gates.bun run typecheck && bun run check && bun test && bun run build

Complete journey to inspect

  1. Open RoarCAD and select the fabrication-ready indicator.
  2. Create a checkpoint and open it in a clean browser profile.
  3. Continue only after downloading the local backup.
  4. Preview a component move and confirm the revision identifier is unchanged.
  5. Use the visible Approve & apply button and confirm a new revision appears.
  6. Return a checkpoint and inspect the common ancestor and semantic diff before adopting.
  7. Open PocketRoar and confirm engineering export remains distinct from fabrication readiness.

Known limits

Audit trail: inspect the CI history, test source, and evaluation records.