Status dokumen bukan klaim bahwa fiturnya sudah tersedia.
RFC dan proposal mencatat rancangan. Untuk kemampuan yang benar-benar dapat dipakai, lihat matriks kapabilitas runtime dan catatan rilis.
YAZA Proposals
Proposals record design directions and do not imply implementation, even when the direction has been accepted. The code-backed implementation status remains in the runtime capability matrix, Appendix G status, and Appendix H status.
| Proposal | Status | Scope |
|---|---|---|
| YAZA-owned data, media, analytics, and web modules | Accepted design direction — staged implementation in progress | CSV, spreadsheets, PDF, images, audio, video, statistics, and web foundations |
| YAZA UI design system | Accepted product direction — implementation pending | YAZA-owned visual identity, primitives, components, accessibility, responsive web, and future mobile renderers |
| YAZA Pulse real-time and event streaming engine | Accepted design direction — implementation pending | Typed sessions, WebTransport/WebSocket/SSE adapters, and a durable partitioned pub/sub broker with replay and consumer groups |
| YAZA Atlas maps engine | Draft proposal — awaiting owner review | YAZA-owned geospatial kernel, renderer, tile pipeline, offline packs, and later search/routing |
| YAZA ecosystem module roadmap | Draft proposal — awaiting owner review | First-party package catalog, dependency layers, integration contracts, and delivery order |
| YAZA database driver architecture | Recommended architecture — implementation staged by API priority | PostgreSQL-first pure-YAZA API integration, then provider-specific relational, embedded, key-value, and document engines |
| YAZA Base SQL database | Proposal — design accepted for planning; implementation not started | YAZA-owned embedded and client/server SQL engine, durable storage, typed variants, WAL-based CDC, Async VFS, and schema-safe rolling migrations |