RFCs — Overview
Spec-level decisions go through the RFC process. Six RFCs are ratified and shipped in v0.3:
| RFC | Title | Status |
|---|---|---|
| RFC-000 | Design rationale | ratified |
| RFC-001 | Relation kind enforcement | ratified |
| RFC-002 | Rule expression grammar | ratified |
| RFC-003 | Events on ui_view | ratified |
| RFC-004 | field reference resolution | ratified |
| RFC-005 | Profile system | ratified |
Authoritative sources live at atomprd/specs/rfcs/. The pages here are summaries with links back to the full text.
Process (post-launch)
Section titled “Process (post-launch)”Spec changes follow Bullet RFC-style:
- Open a discussion issue at
github.com/atomprd/atomprd-format-spec(planned post-launch). - Once direction is rough-agreed, file an RFC PR adding
specs/rfcs/RFC-NNN-<slug>.mdwith sections: Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. - Merge requires two approvers from the spec maintainers + a 5-day comment window.
- After merge, the RFC is ratified. Implementation lands in
@atomprd/specas part of the next minor.
Numbering
Section titled “Numbering”- RFC-000 is the foundational design rationale; subsequent RFCs build on it.
- Numbers are assigned at PR merge time, not draft time.
- Withdrawn / superseded RFCs are marked but not deleted.
Cross-references
Section titled “Cross-references”The SenLang spec also has its own RFC stream. AtomPRD RFCs that touch the bridge reference the corresponding SenLang RFC by number — e.g. AtomPRD’s criterion.behavior.before_after lowering ties into SenLang RFC-0010 Scenario fixtures.