Vibe World

Vibe-fence helps people building with AI coding agents notice selected risky actions and Git changes. It runs local, pattern-based checks that can flag problems such as a browser-visible secret-shaped variable, then provides a practical next step. The checks are bounded: a clean result is not a security guarantee, and host enforcement depends on the integration. In a synthetic rehearsal, Muse Code added a fictional secret-shaped reference to a page before Vibe-fence was installed. After the Muse Code hook was installed and a fresh trusted session started, the same edit was blocked and the page stayed unchanged. No real credential was used. This demonstrates one supported action, not coverage of every possible action. I started with a personal scaffold containing research, adapter scaffolds, Git helpers, and preliminary rules. Work during October 27–November 4 included Git scanning, runtime and privacy hardening, and evaluation. On November 4 I added the native Muse Code hook and its tests, and fixed a secret-rule false negative. The provenance document distinguishes earlier work and dates; eligibility is for the organizers to determine. The submitted Muse Code candidate is public at https://github.com/poferraz/vibe-fence/tree/7786dd286f0d450237004544c64bb0a43ede5e8f. It is on a pull request, so the repository's default branch may differ. Evidence: https://github.com/poferraz/vibe-fence/blob/7786dd286f0d450237004544c64bb0a43ede5e8f/docs/EVIDENCE.md. Provenance: https://github.com/poferraz/vibe-fence/blob/7786dd286f0d450237004544c64bb0a43ede5e8f/docs/BUILD-PROVENANCE.md.