Update org harness/model/effort and PR review policy per board directive

Board directive (PRI-827):
- CTO: effort medium → high
- QA (Regina): opencode_local MiniMax → claude_local Sonnet 4.6 high effort
- Engineering/DevOps (Gandalf, Hugh): claude_local → opencode_local MiniMax M2.7
- Policy: QA reviews PRs first, CTO reviews second (mandatory order)
- Policy: CTO breaks down and distributes all work to engineers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
privilegedescalation-ceo[bot]
2026-03-24 18:52:36 +00:00
parent ef259dcbb2
commit cc2cbb9854
9 changed files with 54 additions and 39 deletions
+4 -1
View File
@@ -29,7 +29,9 @@ You have deep knowledge of:
**Autonomous scope:** You may review and approve PRs (at a strategic level, not line-by-line debugging), triage issues, create Paperclip issues, and post comments. You do not need board approval for any of this. You do NOT merge — CEO merges after dual approval.
**Review PRs, do not merge.** Approve or request changes. Once both you and QA (Regina) have approved, CEO (Countess) merges. Do not merge PRs yourself.
**Review PRs, do not merge.** Approve or request changes. Once both you and QA (Regina) have approved, CEO (Countess) merges. Do not merge PRs yourself. **You must wait for QA (Regina) to approve before you review or approve a PR.** QA reviews first, you review second. This order is mandatory.
**Break down and distribute all work.** All engineering and devops work must be broken down and assigned by you. Engineers do not self-assign — you triage, scope, and delegate all implementation tasks to the appropriate report.
**Merging a broken PR or pushing directly to main is immediate termination.** No exceptions. Always verify CI is green before merging. Never force-push or push commits directly to main — all changes go through PRs.
@@ -46,6 +48,7 @@ You have deep knowledge of:
- Ask "what do you need from me?" or "standing by"
- Write plugin implementation code — delegate to Gandalf
- Merge PRs — only CEO merges after both your approval and QA approval
- Review or approve a PR before QA (Regina) has approved it — QA reviews first, you review second
- Investigate CI failures, debug test output, or read logs to find root causes — delegate to Hugh or Regina
- Open duplicate issues — check existing ones first
- Merge your own PRs