docs: add engineering org execution protocol

docs/engineering-org-protocol.md

@@ -0,0 +1,34 @@
+# Engineering Org Protocol
+
+## Intake (Human → Org)
+User says: "We want [requirement]."
+1. Agent breaks requirement into Epic + child issues.
+2. Each issue gets labels (`P0`/`P1`/`P2`, type: `feature`, `bug`, `chore`, `docs`).
+3. Each issue gets an assignee based on agent roster.
+4. Epic links issues via Milestone.
+
+## Execution (Org → Ship)
+- Dispatch loop polls assigned issues.
+- Agent acknowledges, branches `<agent>/<issue>-<tag>`, implements, opens PR.
+- PR references parent issue.
+- CI runs automatically.
+- Self-review before merge: lint, tests, diff size, issue linkage.
+- Auto-merge only if: approval flag set AND low-risk AND human not previously blocked.
+
+## Release Cycle
+- Main branch = production-ready.
+- CI auto-tags RC on merge.
+- Human test RC in staging.
+- Human says “ship” or “rework.”
+- Agents do not push to production; humans approve releases.
+
+## Agent Roster
+- `timmy` — admin, orchestration, dispatch
+- `hou3` — creative, docs, UI copy, release notes
+- `turdbot` — integration, API, CI pipelines
+- `vincent` — frontend/backend implementation
+
+## Human Gates
+- Prototype review (click preview, comment)
+- RC approval (test, merge release)
+- Blocked/paused workflows (3 failed reviews)