The ĀML Request for Comments process is the public design record for changes that affect language semantics, accountability protocols, policy behavior, interoperability, or conformance.
- Draft — open design proposal; not a compatibility promise.
- Accepted — approved direction for the reference implementation/specification.
- Implemented — present in
aml-coreand covered by tests. - Superseded — replaced by a later RFC.
| RFC | Title | Status |
|---|---|---|
| 0001 | Abstract Meaning Tree | Implemented |
| 0002 | Render Decision Protocol | Implemented |
| 0003 | Accountable Execution Receipt | Implemented |
| 0004 | User-Owned Policy Profiles | Draft |
An RFC should state motivation, scope, data model, security/privacy implications, compatibility impact, test/conformance expectations, and explicit non-goals.
The RFC process does not turn a research hypothesis into an empirical fact. Claims about human attention, wellbeing, accessibility, or ethics still require independent evidence appropriate to those claims.