diff --git a/contracts/README.md b/contracts/README.md
index 863f55f..b673a3a 100644
--- a/contracts/README.md
+++ b/contracts/README.md
@@ -29,6 +29,7 @@ Demand-side analyses that score “gaps versus v3” should be read with this ch
 - [schemas/events/](schemas/events/): Event taxonomy, [event-envelope-base.schema.json](schemas/events/event-envelope-base.schema.json), discriminated [event-envelope.schema.json](schemas/events/event-envelope.schema.json), and specializations.
 - [fixtures/v3/](fixtures/v3/): Machine-validated example payloads for the validator.
 - [companion/](companion/README.md): Optional interoperability schemas (`CampaignPlan`, `DataMovementIntent`, `EvalPublication`) for enterprises that adopt the **core-v3-companion** bundle (see [profiles/core-v3-companion.json](profiles/core-v3-companion.json)).
+- [rfcs/](rfcs/README.md): Draft RFCs for contract changes (platform alignment and related proposals).
 - [GAP_DISPOSITION_REGISTER.md](GAP_DISPOSITION_REGISTER.md): Maps consolidated workflow themes to spine vs companion vs capability disposition.
 - [v3-design-notes.md](v3-design-notes.md): Unification decisions (identity, runs, errors, events).
 - [v3-release-governance.md](v3-release-governance.md): Stub release and GA policy (expand with real thresholds later).
diff --git a/contracts/rfcs/001-run-invocation-and-tool-use.md b/contracts/rfcs/001-run-invocation-and-tool-use.md
new file mode 100644
index 0000000..d4e7649
--- /dev/null
+++ b/contracts/rfcs/001-run-invocation-and-tool-use.md
@@ -0,0 +1,14 @@
+# RFC 001: Run invocation I/O and MAG tool_calls
+
+## Problem
+
+core-v3 `execution-context.schema.json` describes reproducibility hashes only. Platform v0 sends `inputs` (messages, tools, prompt) and `parameters` (model, system) and returns `outputs.tool_calls` as `[{ id, name, input }]`.
+
+## Proposal
+
+- Add companion schema `run-invocation.schema.json` OR extend profile with `x-gmp` invocation block.
+- Document OpenAI/Anthropic interop and MAG normalization.
+
+## Platform reference
+
+[ARIAPlatform `platform-v0-implementation-profile.json`](https://github.com/brettin/ARIAPlatform_v0/blob/main/reference/platform-v0-implementation-profile.json) — `ExecutionContextSubmit`, `MagToolCall`, `RunOutputs`.
diff --git a/contracts/rfcs/README.md b/contracts/rfcs/README.md
new file mode 100644
index 0000000..1453cae
--- /dev/null
+++ b/contracts/rfcs/README.md
@@ -0,0 +1,23 @@
+# Spec RFCs
+
+Draft RFCs for GMP core-v3 contract changes proposed from [ARIAPlatform](https://github.com/brettin/ARIAPlatform_v0) alignment work. Open one PR per RFC; track gap IDs from the platform [`spec-implementation-gap-register.json`](https://github.com/brettin/ARIAPlatform_v0/blob/main/reference/spec-implementation-gap-register.json).
+
+| RFC | Title | Priority |
+| --- | --- | --- |
+| [001](001-run-invocation-and-tool-use.md) | Run invocation I/O and MAG tool_calls | P0 |
+| [002](002-tool-call-events-vs-llm-tool-use.md) | tool.call events vs LLM tool-use | P0 |
+| [005](005-events-append-list.md) | Events append/list DTO | P1 |
+| [003](003-run-status-vocabulary.md) | Run status enum | P1 |
+| [004](004-budgets-allocate-enforce.md) | Budget allocate and enforce | P1 |
+| [006](006-capability-registry-platform.md) | Capability registry vs spec Capability | P2 |
+
+## Suggested merge order
+
+1. RFC 001 — Run invocation I/O and MAG `tool_calls`
+2. RFC 002 — `tool.call` events vs LLM tool-use
+3. RFC 005 — Events append/list DTO
+4. RFC 003 — Run status vocabulary
+5. RFC 004 — Budget allocate and enforce
+6. RFC 006 — Capability registry vs spec `Capability`
+
+Until an RFC merges, platform v0 may continue to document wire behavior in [`platform-v0-implementation-profile.json`](https://github.com/brettin/ARIAPlatform_v0/blob/main/reference/platform-v0-implementation-profile.json).