RFC Status
This specification is under active internal development by SpeakEZ Technologies. As the Clef language and its compiler toolchain mature, the normative content in this document is likely to see substantial revision. Chapters may be added, reorganized, or rewritten as implementation experience reveals better formulations.
Change Process
Clef will adopt a two-track process for evolving the language and its specification:
RFC (Request for Comments)
An RFC proposes a concrete change to the Clef language or specification. RFCs are appropriate when:
- A new language feature is proposed
- An existing feature’s semantics need revision
- A normative section of the specification requires amendment
Each RFC will include a motivation, a detailed design, and an analysis of the impact on existing Clef code. RFCs proceed through draft, review, and accepted (or rejected) stages.
RFD (Request for Discussion)
An RFD opens a broader design discussion without committing to a specific proposal. RFDs are appropriate when:
- A problem area has been identified but the solution space is not yet clear
- Multiple competing approaches exist and community input would inform the direction
- Cross-cutting concerns affect several areas of the language or toolchain
RFDs may lead to one or more RFCs, or may conclude that no change is needed.
Current Status
The RFC/RFD process is not yet active. It will launch when the initial language design and specification have been formalized to a stable baseline. Until then, changes to this specification are made directly by the core development team.