# RFCs — Request for Comments

RFCs are the primary mechanism for proposing significant changes to JamJet. An RFC is required for anything that modifies the public SDK, API contracts, IR schema, agent card spec, or protocol adapters.

---

## RFC Process

1. **Draft** — Copy `RFC-000-template.md`, fill in the template, open a PR
2. **Discussion** — Team reviews in the PR; author iterates
3. **Accepted** — PR merged; implementation can begin
4. **Implemented** — RFC marked as implemented, linked to code PRs
5. **Superseded** — A newer RFC replaces this one; old RFC marked superseded

RFCs are never deleted. Superseded RFCs are preserved with a note pointing to the replacement.

---

## Current RFCs

| RFC | Title | Status |
|-----|-------|--------|
| [RFC-001](RFC-001-execution-model.md) | Execution Model | Draft |
| [RFC-002](RFC-002-ir-schema.md) | IR and Schema System | Draft |
| [RFC-003](RFC-003-storage-durability.md) | Storage and Durability Model | Draft |
| [RFC-004](RFC-004-python-sdk.md) | Python SDK Design | Draft |
| [RFC-005](RFC-005-agent-model.md) | Agent Model | Draft |
| [RFC-006](RFC-006-mcp-integration.md) | MCP Integration | Draft |
| [RFC-007](RFC-007-a2a-integration.md) | A2A Integration | Draft |
| [RFC-008](RFC-008-protocol-adapters.md) | Protocol Adapter Framework | Draft |

---

## RFC Template

See `RFC-000-template.md` for the standard template all RFCs must follow.
