Vibe Code Chaperone -- Because the Demo Works Is Not a Security Model

It generated twelve files, chose a database, and deployed itself. Does anybody in the room know why it works?

Vibe Code Chaperone supervises AI-assisted software before a convincing demo becomes an accidental production system. It binds review to an exact commit, runs the project's real checks, tests failure paths, inspects security and persistence boundaries, and identifies who actually owns the behavior.

What you get

• A VIBES ONLY, CHAPERONED DEMO, REVIEWABLE, or PRODUCTION CANDIDATE verdict
• Proven and unproven behavior separated
• Authentication, authorization, secret, input, persistence, and rollback review
• Missing tests and likely demo illusions
• Human ownership for every unresolved production behavior
• Exact checks and the smallest route to the next state

It does not shame beginners, reject code because AI helped write it, or promote a demo because the happy path sparkles. It also does not merge or deploy.

Pair with Release Candidate Audit when the whole immutable commit needs an independent GO or NO-GO.