governance: enforce strict Questions→Proposal→Plan gates with explicit approval phrases; add branching proposal; mark plan pending; audit checks sequencing
Some checks failed
ci / test (push) Has been cancelled

This commit is contained in:
2025-09-17 11:25:05 -05:00
parent 1eaa2f7997
commit e925e6ebca
11 changed files with 167 additions and 3 deletions

View File

@@ -0,0 +1,9 @@
# 02 — Branching/Release — Proposal (LLM)
- Goal: Keep `main` always green and production-ready with CI protections, while developing on short-lived branches.
- Recommended model: Trunk-based. Optional `next` only for batching risky work.
- Main content: full repo (code, prompts, templates, docs). Release tags: `YYYY-MM-DD-HHMM` on `main` only.
- Protections: required checks (audit + Docker tests), PRs required, Conventional Commits, linear history/squash.
- Migration: tag baseline; create `wip/phase1`; enable protections; add docs/branching.md.
Approve by replying in the human doc with “Approved for Plan”.