vibe

1# Vibe Governed Runtime Entry
2 
3This file is the host-facing SOP for entering canonical `vibe`. Keep it small: runtime details belong in `protocols/runtime.md`, execution discipline belongs in `protocols/do.md`, and host wrapper recipes belong in installer-generated wrapper docs.
4 
5## Trigger Contract
6 
7Enter canonical `vibe` before ordinary execution when the user explicitly invokes `$vibe`, `/vibe`, or the `vibe` skill, or when the host intentionally chooses governed requirement/plan/execution closure for a complex task.
8 
9Do not route every loosely related task into `vibe`. Lightweight questions,
10single-command checks, or tasks better served by another explicitly requested
11skill may proceed outside `vibe` unless the user explicitly invoked this entry.
12 
13Installed-copy updates use `update --skills-dir <skills-dir>` on the same managed directory.
14 
15User instructions, including CLAUDE.md, GEMINI.md, AGENTS.md and direct workflow limits such as TDD exceptions, remain highest priority. Preserve canonical launch and proof rules within those limits.
16 
17## Canonical Bootstrap
18 
19`vibe` is a host-syntax-neutral skill contract. Before canonical launch, do only the minimum needed to launch:
20 
21- Resolve `skill_root` and `workspace_root`.
22…