RFC dan proposal mencatat rancangan. Untuk kemampuan yang benar-benar dapat dipakai, lihat matriks kapabilitas runtime dan catatan rilis.
YAZA RFCs
This directory contains approved design decisions for unresolved language, runtime, framework, and security work. All eight RFCs were accepted by the project owner on 2026-10-23. Acceptance approves their design direction; it is not a claim that the features are implemented or production-ready.
Each accepted RFC records its decision date. Future RFC status changes must include a dated decision and rationale. The accepted designs still need to be incorporated into the normative language specification and implementation plan; unresolved details listed under “Open questions” remain open until those documents are updated.
Proposal index
| RFC | Title | Main blueprint areas | Status |
|---|---|---|---|
| RFC 0001 | Core Types, Nullability, and Errors | G.1, G.3, G.5, G.6, G.10, H.4 | Accepted |
| RFC 0002 | Memory, Ownership, and Unsafe Boundaries | G.1, G.3, H.4, H.5, H.7 | Accepted |
| RFC 0003 | Modules, Packages, and Supply-Chain Metadata | G.2, G.4, H.6, H.11, H.14, H.17 | Accepted |
| RFC 0004 | Executable Layered APIs and PostgreSQL | G.5–G.18, H.8, H.10, H.12 | Accepted |
| RFC 0005 | Structured Concurrency and HTTP Runtime | G.14, G.15, G.17, G.18, H.7, H.8 | Accepted |
| RFC 0006 | Secure Standard Library and Cryptography | G.7, G.12, G.18, H.8–H.13 | Accepted |
| RFC 0007 | Diagnostics, Testing, and Release Evidence | G.16, G.18, H.1–H.3, H.6, H.14–H.18 | Accepted |
| RFC 0008 | Linux, WebAssembly, Edge, and Mobile Targets | G.18, G.19, H.13 | Accepted |
RFC lifecycle
Allowed statuses are Proposed, Accepted, Rejected, Deferred, and Superseded. Status changes must include a dated decision and a short rationale in the RFC and this index. Here, Accepted records the project owner's approval of the design direction. A normative specification, implementation, security review, and conformance tests are still required before claiming the related feature or guarantee is delivered.
Current implementation boundary
The runtime capability matrix, Appendix G status, and Appendix H status remain the source of truth for code that currently exists. RFC acceptance does not change those implementation statuses. In particular, it does not make YAZA memory-safe, production-ready, or complete for web, database, WASM, or mobile development.