Sample guide
What a Mapparoo audit looks like.
This is a real audit guide from a sample project — plan vs build, verification status, and decision briefs. The interactive guide renders below; the prose on this page is what search engines and readers without JavaScript see.
Coverage statement
The sample audit read planning documents and analyzed a pinned repository snapshot. Tests were executed for recognized Node/TypeScript setups. Areas not examined are listed in the guide's coverage banner — never silently absorbed.
Example findings (restated as text)
Password reset flow
Planned in §4.2, found in code, with tests executed in the audit environment. Verified to tier 2 — declared build and tests completed.
Email notifications
Planned in §6.1, present in code, but no evidence of execution was found. Shown as unverified — an ordinary, honest state.
Stripe webhook handling
Planned in §9, not found in this snapshot. A gap with high product impact — customers could pay and receive nothing.
What verified, unverified, and gap mean
Verified
Names its evidence tier — for example, declared build and tests completed in the audit environment. Never overclaims beyond what the evidence establishes.
Unverified
Present in code but no execution evidence yet. Calm gray, not an alarm.
Gap
Something planned but missing, or a divergence that matters. Each gap arrives as a decision with pinned evidence.
Interactive sample
The guide below runs in a sandboxed frame. It makes no external requests and needs no account.