RFC Process

Every capability is designed in writing before it is built.

EKOS is RFC-first. No feature is implemented until its RFC is accepted, and RFCs are written just-in-time, before the phase that needs them.

Workflow

1. Design — write an RFC before any code.
2. Architecture review — validate against the compiler model.
3. Interfaces — define public traits and types first.
4. Tests — before implementation.
5. Implementation, refactoring, documentation.
6. Integration and, for performance-relevant changes, benchmarks.
7. Merge.

Where RFCs live

docs/rfcs/ (0001–0024) and ekos/docs/rfcs/ (0025 onward). Check both directories for the highest existing number before choosing one — two RFCs have collided on the same number before.

Statuses

Proposed / Draft → Accepted → implemented → (Superseded or Withdrawn).

Index

166 RFCs in total. Each project session also writes a devlog — the project's long-term memory of what shipped, why, and what was learned.