docs/rfcs/README.md

<!-- SPDX-License-Identifier: Apache-2.0
     https://www.apache.org/licenses/LICENSE-2.0 -->

<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*

- [Design RFCs](#design-rfcs)
  - [The RFCs](#the-rfcs)

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

# Design RFCs

A decision that shapes the framework — a new trust boundary, a new install
mechanism, a rule every skill has to obey — gets written down before it is
built. These are those documents: the reasoning, the alternatives that were
rejected, and what adopting the design commits the project to.

An RFC is a record, not a manual. Once one is implemented, the rules it
settled live in the docs describing the thing itself; the RFC stays behind
as the explanation of *why* those rules are the way they are.

## The RFCs

| RFC | Title | Status |
|---|---|---|
| [RFC‑AI‑0002](RFC-AI-0002.md) | Secure Agents setup | Implemented |
| [RFC‑AI‑0003](RFC-AI-0003.md) | Privacy-aware LLM routing for foundation private information | Provisional — pending ASF Privacy VP / Legal |
| [RFC‑AI‑0004](RFC-AI-0004.md) | Principles of agentic interaction for open-source maintainers | Implemented |
| [RFC‑AI‑0005](RFC-AI-0005.md) | Framework taxonomy | Implemented |
| [RFC‑AI‑0006](RFC-AI-0006.md) | Trusted external skill sources | Partially implemented (Phase A) |
| [RFC‑AI‑0007](RFC-AI-0007.md) | Selective snapshot — fetch only the chosen skill families | Proposed |
| [RFC‑AI‑0008](RFC-AI-0008.md) | The coordinator role — multi-hop relay of security reports | Draft |

Every RFC carries its own **Status of this document** section. That section
is the authoritative one if this table has fallen behind.