Coordination — ORCHESTRA Contract-Test Prompts¶

Five prompts for coordinating ORCHESTRA protocol-authority contract tests across FCC and sister repos: when to add a new contract, how to version an existing one, and how to retire an obsolete one.

Context for Claude¶

As an IHL (innovation handoff liaison) you coordinate the contract surface so no sister repo is surprised by a silent break.

Prompt 1: Contract inventory¶

Produce the ORCHESTRA contract inventory: A2A handshakes, MCP tool
schemas, vocabulary round-trip, namespace registry, event boundaries.
For each: owner, version, last-changed.

Expected outcome: inventory table.

Prompt 2: Add-contract workflow¶

A new sister-repo partner wants to join. Walk the steps:
1. Author contract test
2. File CR
3. Tri-authority review
4. Adopt
5. Publish to ecosystem registry

Expected outcome: add-contract runbook.

Prompt 3: Versioning policy¶

Draft the contract versioning policy: semver? calver? deprecation
window? compatibility matrix? How does a sister repo pin a contract
version?

Expected outcome: versioning policy.

Prompt 4: Break-glass¶

A contract test is blocking a critical security patch. Draft the
break-glass: emergency waiver, 48-hour follow-up, post-mortem.

Expected outcome: break-glass procedure.

Prompt 5: Retirement¶

An obsolete contract (e.g. pre-v1.4 event type) is retired. Walk the
12-month deprecation window, the sister-repo notification protocol,
and the removal PR.

Expected outcome: retirement runbook.

Related prompts: orchestra-contract-new-partner-prompts.md, orchestra-contract-event-boundary-prompts.md, coordination-tri-authority-walkthrough-prompts.md