Governance Framework¶
How authority works, who decides what, and how we resolve conflicts.
Authority Matrix (Current State)¶
| Authority Type | Holder | Examples | Status |
|---|---|---|---|
| Doctrine | raos-agent, Wisut Punnaraj | alpha_workspace, core-principles | CLEAR |
| Registry | punnaraj-over-view | System inventory, relationships | CLEAR |
| Operational | Punnaraj-api, Operations team | Runtime, API endpoints | CLEAR |
| Control Planes | mcp-cloudflare, mcp-github | Who can deploy to Cloudflare/GitHub | ⚠️ OVERLAPPING |
| Security | magga-940-secretman | Credential management | CLEAR |
| Governance | pun-policy, continuity | Rules, succession | CLEAR |
| Family | punnaraj-family, continuity | Family operations, data | CLEAR |
9 Clarifications Needed ⚠️¶
High Priority (Blocks Command Center)¶
1. mud vs magga-mud - Both are Mutual Understanding Document workspaces - Question: What's the difference? Different publication targets? Different scope? - Impact: Affects documentation strategy - Status: BLOCKED
2. punnaraj-system vs core-principles - Both claim foundational authority - core-principles is public; punnaraj-system role unclear - Question: Which is canonical? Different purposes? - Impact: Affects doctrine layer clarity - Status: BLOCKED
3. punnaraj-cloudflare-control vs mcp-cloudflare - Both Cloudflare control planes - MAGGA-114 vs generic implementation - Question: Same thing or parallel implementations? When use which? - Impact: Affects control plane design - Status: BLOCKED
Medium Priority (Affects Operations)¶
4. punnaraj-mcp vs magga-mcp-server - Two MCP servers on Workers - Question: Same or different? What does each do? - Impact: Affects integration design - Status: INVESTIGATE
5. pun-policy vs core-principles - Both establish rules/principles - Question: Policy vs principles? Different documents? - Impact: Affects governance clarity - Status: INVESTIGATE
6. codex-workspace purpose - Repository exists but purpose unclear - Question: What is this? Active or archived? - Impact: Affects project cleanup - Status: CLARIFY
Low Priority (Administrative)¶
7. nemesis / Magga-Nirvana - Experimental workspace - Question: Still active? Archive? - Impact: Cleanup decision - Status: CLARIFY
8. meta-ops-console - Lovable project (UI builder) - Question: Active or experimental? Keep or deprecate? - Impact: Tool strategy - Status: CLARIFY
9. metax-sbs.github - Organizational repository - Question: What's the relationship to Punnaraj? - Impact: Organizational structure clarity - Status: CLARIFY
Decision Protocol¶
How Decisions Get Made¶
- Proposal — Suggest change, document reasoning
- Consultation — Ask relevant authorities
- Evidence — Gather facts, document sources
- Decision — Clear approval from authority
- Documentation — Record decision + reasoning in appropriate repository
- Audit Trail — Keep decision history for learning
Authority Levels¶
| Level | Can Decide | Examples |
|---|---|---|
| Personal | Individual choice, no approval needed | How I use tools, personal data |
| Operational | Punnaraj-api owner + ops team | What runs, how it runs, deployment |
| Governance | Wisut Punnaraj + pun-policy | System rules, authority boundaries |
| Constitutional | Wisut Punnaraj only | Core philosophy, family decisions |
Known Conflicts to Resolve¶
Doctrine Conflict¶
- Issue: Multiple repositories claim to be "canonical doctrine"
- Risk: Agents don't know which to trust
- Resolution: Create explicit doctrine hierarchy in core-principles
Control Plane Conflict¶
- Issue: Two Cloudflare control paths (mcp-cloudflare + punnaraj-cloudflare-control)
- Risk: Unclear which to use when
- Resolution: Clarify MAGGA-114 vs bootstrap, document decision tree
Documentation Conflict¶
- Issue: Multiple documentation sources (mud, magga-mud, punnaraj-docs, command-center)
- Risk: Inconsistent information
- Resolution: Create documentation hierarchy in punnaraj-docs
Succession Planning¶
Primary Authority Holder: Wisut Punnaraj
Deputy: [UNKNOWN — Needs documentation]
Backup: [UNKNOWN — Needs documentation]
Action Items: - [ ] Document succession chain - [ ] Train first deputy - [ ] Create handoff procedures - [ ] Test continuity plan
Review Cycles¶
| Frequency | What | Owner |
|---|---|---|
| Weekly | Operational status, blockers | Punnaraj-api team |
| Monthly | Authority clarity, conflicts | Wisut Punnaraj |
| Quarterly | Roadmap progress, resource allocation | Strategic review |
| Yearly | Doctrine review, philosophy evolution | Constitutional review |
Next Steps¶
- This week: Answer the 9 clarification questions
- Next week: Update authority matrix with answers
- Next month: Cascade clarity to all 32 repositories
- Ongoing: Use command-center dashboard to flag new conflicts
Status: EXPERIMENTAL — This framework is being built as we use it. Feedback welcome.