Last updated Jun 14, 2026

API Council weekly agenda

The API Council meets every Tuesday, 13:00 UTC for 30 minutes. The agenda is auto-generated from apps/docs/content/docs/process/ artefacts every Monday and posted in #api-council.

Standing agenda

0. Roll call (2 minutes)

Quorum: ≥ 1 engineer per bounded context, ≥ 3 total.

Bounded contexts represented:

• Authority
• Entity lifecycle
• Equity
• Documents
• Compliance
• Operations
• Platform
• Customer

1. Spec PRs in review (10 minutes)

Auto-pulled from open PRs labelled spec:api-council. Each PR walks through:

• Resource + operation introduced.
• Spec extensions applied (x-matter-*).
• MCP exposure decision.
• Bounded-context fit.

Council outcomes: approve / revise / escalate / reject.

2. Production-readiness promotions (10 minutes)

Auto-pulled from open PRR docs at apps/api/__gates__/prod-readiness/. For each promotion request, the bounded-context owner walks through the PRR checklist.

Council outcomes: promote to Beta / promote to GA / hold for revision.

3. Deprecation queue (3 minutes)

Auto-pulled from apps/docs/content/docs/process/deprecation-policy declarations. Review:

• Endpoints entering 90-day deprecation window.
• Endpoints approaching sunset (≤ 30 days).
• Customers still on deprecated endpoints (top 10 by traffic).

4. Chaos + drill cadence (3 minutes)

Auto-pulled from apps/api/lib/chaos-cadence.ts status snapshot. Review:

• Overdue drills.
• Drills due in the next 7 days.
• Game day status (quarterly).

5. Pentest + bug-bounty triage (2 minutes)

Auto-pulled from apps/api/lib/pentest-tracker.ts + apps/api/lib/bug-bounty.ts. Review:

• New findings since last week.
• Critical findings approaching SLA.
• Closed findings + action-item completion.

Adjourn

Decisions logged at apps/docs/content/docs/process/council-decisions/<YYYY-MM-DD>.mdx.

Special agendas

When triggered, the council convenes for a focused session:

• Breaking-change discussion — required when oasdiff flags a breaking change without override. 2-hour deep-dive.
• Incident retrospective — within 14 days of any SEV1 / SEV2.
• Maturity-ladder review — quarterly review of every endpoint's maturity stage + sunset clock.

Forum hygiene

• Async first — every agenda item must have a written brief posted ≥ 24h before the meeting.
• Time-boxed — items running over time are deferred to the next week; the council does not extend.
• Recorded — every meeting recorded; transcript posted in #api-council. Recordings retained for 90 days.
• Decisions binding — Council decisions are recorded as RFCs at apps/docs/content/docs/rfcs/.