Control-plane RFCs

Purpose

This directory holds control-plane RFC examples and drafts for AI workflow, agent orchestration, and cross-repo process changes.

Canonical implementation RFCs still live in docs/development/rfcs/ unless the maintainer explicitly decides to move them here.

Control-plane RFCs are manual opt-in only. Do not create one during normal Direct Implementation Mode.

When To Write An RFC

Recommend an RFC when any apply, but write one only after the user explicitly opts in:

• New app type.
• New backend architecture.
• App contract changes.
• Cross-package or cross-repo changes.
• New dependency or framework.
• Auth, billing, or data model changes.
• Public API or deployment impact.
• High uncertainty that deserves discussion.

Naming

YYYY-MM-DD-short-kebab-title.md

RFC Sections

• Context
• Problem
• Goals
• Non-goals
• Options
• Proposed direction
• Risks
• Acceptance
• Rollout plan
• Open questions

Relationship To ADRs

RFCs explore. ADRs record decisions. One RFC can produce one or more ADRs.