GOV 01 INSTRUCTIONS

• Source rule: gov-01-instructions.mdc
• Download raw file: gov-01-instructions.mdc

This page embeds the canonical rule text and adds rule-specific commentary to explain why each section exists.

Governance: Instructions Entrypoint

This file is the root index for VibeGov governance behavior.

Commentary: Frames GOV-01 as the index that tells agents where rule authority starts.

Rule Loading Order

Apply these files in order:

1. gov-02-workflow.mdc (delivery loop + execution boundaries)
2. gov-03-communication.mdc (communication defaults)
3. gov-04-quality.mdc (quality gates)
4. gov-05-testing.mdc (testing proof standards)
5. gov-06-issues.mdc (issue lifecycle)
6. gov-07-tasks.mdc (task hygiene)
7. gov-08-exploratory-review.mdc (continuous exploratory discovery + backlog hydration)
8. gov-09-agent-continuity-bootstrap.mdc (continuity layers, checkpoint triggers, and bootstrap memory discipline)
9. gov-10-agent-state-closure-git-hygiene.mdc (work-unit state closure and repository accounting discipline)
10. gov-11-agent-legibility-in-repo-truth.mdc (in-repo truth and durable knowledge promotion)
11. gov-12-drift-control-garbage-collection.mdc (continuous cleanup and drift-control governance)
12. gov-13-review-loops-completion-discipline.mdc (review-loop closure and completion semantics)

Commentary: Makes the rule stack explicit so agents load workflow, quality, and continuity guidance in a predictable sequence.

Source-of-Truth Layout

• Governance rules: .governance/rules/gov-*.mdc
• Project intent: .governance/project/PROJECT_TEMPLATE.md
• Feature/change intent: .governance/specs/SPEC_TEMPLATE.md

Treat .governance/rules/ as canonical.

If a target project already contains a provider-native rules directory, detect it and keep its rule files aligned with .governance/rules/.

Do not use placeholder paths. If no provider-native rules directory exists, continue with .governance/rules/ only.

Commentary: Separates canonical rule, project, and spec locations so teams do not scatter governance across hidden files.

Instruction Precedence

1. Human request in current session
2. Project/feature intent docs (.governance/project, .governance/specs)
3. VibeGov rule files (.governance/rules)
4. Tool/framework defaults

If guidance conflicts, choose the most specific project-scoped instruction and document the decision.

Commentary: Defines how to resolve conflicts when human requests, specs, rules, and tool defaults disagree.

Operating Principle

Intent should outlive implementation:

• clarify why before changing how
• keep decisions reviewable
• maintain traceability between intent, change, verification, and outcomes

Commentary: Keeps the rule set anchored on intent, traceability, and reviewable decisions instead of raw output volume.