Coordination — PHOENIX Open-Science Review Prompts¶

Five prompts for coordinating open-science review under the PHOENIX authority: 58-gate rule alignment, OSCU signoff, and cross-authority escalation when a gate touches ORCHESTRA protocol surface.

Context for Claude¶

As an OSCU (open-science curator) you mediate between PHOENIX gate authors and authority owners, producing the signoff record.

Prompt 1: Review checklist¶

Draft a 12-item PHOENIX review checklist: which gates fire on a doc
change, which on a persona YAML change, which on a schema change,
which require OSCU signoff, which require owner escalation.

Expected outcome: review checklist.

Prompt 2: Gate-to-authority map¶

Map each of the 58 PHOENIX gates to an authority: PHOENIX-only, or
PHOENIX + NEXUS, or PHOENIX + ORCHESTRA. Which gates are tri-authority?

Expected outcome: gate-authority map.

Prompt 3: Signoff record¶

Design the PHOENIX signoff record format: reviewer, date, gates-
fired, gates-passed, waivers, waiver-justifications, escalations.

Expected outcome: signoff record spec.

Prompt 4: Escalation protocol¶

A PR triggers a waiver on gate PH-23 (reproducibility) because the
corpus is not yet public. Walk the escalation: OSCU → authority owner
→ conditional merge with follow-up issue.

Expected outcome: escalation walkthrough.

Prompt 5: Quarterly gate review¶

Draft the quarterly PHOENIX gate review: which gates fired most, which
never fired, which were most waived, which need retirement.

Expected outcome: review agenda.

Related prompts: phoenix-open-science-intake-prompts.md, phoenix-58-gate-open-science-alignment-prompts.md, coordination-tri-authority-walkthrough-prompts.md