ASC Requests for Comments¶
Requests for Comments (RFCs) are the durable mechanism for proposing substantial changes to Agent Status Codes, collecting implementation feedback, and recording why the specification evolved.
The RFC space is open
There are no numbered ASC RFCs yet. Start with the RFC template and open a pull request when a concrete proposal is ready for discussion.
When to write an RFC¶
Use an RFC for a change that affects interoperability or the long-term contract, including:
- a new core status code or lifecycle concept;
- a change to the canonical envelope;
- a new protocol binding or conformance profile;
- a compatibility or versioning rule;
- a security or privacy requirement; or
- a change that existing producers or consumers must consciously adopt.
Small corrections, clearer wording, examples, and objective fixes can be made by a normal pull request.
Lifecycle¶
| Status | Meaning |
|---|---|
| Proposal | Open pull request; the idea is not part of the RFC set |
| Draft | Worth developing and discussing, but not stable |
| Active | Current design or implementation work is underway |
| Accepted | Approved direction and incorporated or scheduled for a specification release |
| Rejected | Considered and deliberately not adopted |
| Superseded | Replaced by a later RFC |
The authority that moves an RFC into a terminal state is TBD while the project is young. Status changes must always be explicit in the RFC and its pull request history.
RFC index¶
| RFC | Title | Status | Target |
|---|---|---|---|
| None | No RFCs published yet | Not applicable | Not applicable |