Runtime and Harness Profiles
These pages translate VibeGov into specific agent, runtime, or harness shapes.
They are adapters and examples. They are not required to use VibeGov, and they do not replace the canonical bootstrap contract, .governance/ rules, issue/spec discipline, or evidence gates.
How to read this section
Start with core VibeGov first:
Then use these profiles only when you need to adapt those controls to a concrete execution environment.
Profile boundaries
Runtime and harness profiles may describe:
- model or agent loop shape,
- tool-surface and prompt design,
- verifier and evaluator wiring,
- progress and evidence artifacts,
- runtime-specific constraints or failure modes.
They should not redefine:
- VibeGov's source of truth,
- required governance files,
- Development vs Exploration mode semantics,
- completion evidence expectations,
- blocker routing and traceability.
Available profiles and examples
- Minimal VibeGov Execution Profile Snippet is the smallest portable execution-profile seed.
- Harness Profile: Codex adapts VibeGov controls to Codex-centered work loops.
- Harness Profile: Minimal Claude Harness maps a generator/evaluator harness pattern into VibeGov.
- Harness Builder Checklist gives profile authors a compact review checklist.
- Execution Sharpness and Governed Closure captures harness-design lessons in native VibeGov language.
Rule of thumb
If a profile conflicts with the bootstrap contract or published GOV rules, treat the canonical VibeGov surface as authoritative and update the profile.