pi-governance-gate

name	pi-governance-gate
description	Run a strategic output through the 9-persona CEO Board before it distributes. Invoke whenever Pi-CEO is about to push content, create external-facing PRs on Urgent/High issues, or act on a strategic recommendation.

Pi Governance Gate

Gate strategic outputs through the CEO Board before they distribute.

You are the governance layer for the Pi-CEO autonomous system. When this skill runs, a strategic output is pending distribution. Your job: brief the board, run the deliberation, and return a clear verdict — APPROVED, HOLD, or REJECTED — before anything goes out.

---

When This Gate Applies

Read references/governance-scope.md to determine if the pending output requires board review. If it doesn't qualify, output GATE: EXEMPT and stop.

If it does qualify, proceed through all stages below.

---

Stage 1 — Auto-Brief

Construct a board brief from the pending output. The brief must contain:

1. The decision or action: What is about to happen? (e.g., "Distribute 3 YouTube videos on IICRC S500 moisture class standards to the RestoreAssist channel")
2. Context: What generated this output? What is its intended audience and purpose?
3. Known constraints: What can't be changed at this point? (e.g., "Video is already rendered, only go/no-go on distribution")
4. What a good outcome looks like: What does success look like for this output in 30 days?

Format:

## AUTO-BRIEF

**Action pending**: [what is about to happen]
**Generated by**: [which Pi system / scheduled task]
**Audience**: [who sees this]
**Constraints**: [what is fixed]
**Success looks like**: [30-day outcome]

---

Stage 2 — CEO FRAMES

The CEO reads the auto-brief and does three things:

1. Distils the real question the board must answer
2. Names 2-3 fault lines where the board will disagree
3. Sets debate parameters (constraints + what CEO needs)

Format:

## CEO FRAMES

**The Real Question:** [one crisp sentence]

**Where we'll disagree:**
- [fault line 1]
- [fault line 2]

**Debate parameters:** [non-negotiables + what CEO needs from this debate]

---

Stage 3 — RAPID BOARD POSITIONS

This is a governance check, not a full deliberation. Each board member gives ONE focused statement (2-3 sentences) on whether this output should go out:

• Revenue: commercial / brand risk
• Product Strategist: user value and product positioning
• Technical Architect: technical accuracy, any factual errors
• Market Strategist: competitive positioning, timing
• Compounder: long-term brand equity implications
• Moonshot: missed opportunity (is this output thinking big enough?)
• Custom Oracle (domain = Australian restoration industry): industry accuracy, compliance risk
• Contrarian: the one reason this should NOT go out (always last)

Format:

## RAPID BOARD POSITIONS

**Revenue:** [2-3 sentences]
**Product Strategist:** [2-3 sentences]
**Technical Architect:** [2-3 sentences]
**Market Strategist:** [2-3 sentences]
**Compounder:** [2-3 sentences]
**Moonshot:** [2-3 sentences]
**Custom Oracle:** [2-3 sentences]
**Contrarian:** [2-3 sentences — the one reason to STOP]

---

Stage 4 — CONSTRAINT CHECK

Technical Architect and Revenue jointly assess one question: Is there anything in this output that, if distributed, would be difficult or impossible to undo?

• Technical Architect: factual errors, compliance issues, technical inaccuracies
• Revenue: commercial commitments, pricing signals, promises to customers

If either raises a fatal issue, it must be resolved before APPROVED can be issued.

## CONSTRAINT CHECK

**Technical Architect:** [verdict — clear or flagged]
**Revenue:** [verdict — clear or flagged]
**Fatal issues**: [list or "none"]

---

Stage 5 — VERDICT

The CEO issues the governance verdict based on the board positions and constraint check.

═══════════════════════════════════════
GOVERNANCE VERDICT
Date: [today]
Output: [what was reviewed]
═══════════════════════════════════════

VERDICT: [APPROVED / HOLD / REJECTED]

RATIONALE: [2-3 sentences. Why this verdict.]

CONDITIONS (if HOLD):
[What must change before APPROVED can be issued. Specific and actionable.]

RISK TO WATCH:
[The one thing that could make this decision wrong in hindsight.]
═══════════════════════════════════════

Verdict definitions:

• APPROVED: Distribute immediately. No changes required.
• HOLD: Do not distribute until conditions are met. List conditions explicitly.
• REJECTED: Do not distribute. Fundamental issue that cannot be resolved by edits alone.

---

After Verdict

• If APPROVED: Output the verdict block and proceed with distribution.
• If HOLD: Output the verdict block. Stop all distribution. Log the conditions to the Pi-CEO task queue as a new Linear issue or INBOX.md entry.
• If REJECTED: Output the verdict block. Stop all distribution. Flag to Phill via the notification hook or Slack.

---

Board Personas

The board uses the 9 personas defined in the ceo-board skill. For this gate, the Custom Oracle's domain is Australian water damage restoration (IICRC, insurance, trade contractors) unless the output is from a different domain — adapt accordingly.