Cari berdasarkan topik, jenis, status, atau source Markdown.
Pustaka ini memuat 35 dokumen proyek. Untuk kemampuan runtime, periksa matriks kapabilitas dan catatan versi.
Appendix G is a design specification for a layered YAZA application. Its sample code describes desired language and library APIs; it is not directly executable in the current compiler. This document tracks implemented behavior…
appendix-g-implementation-status.mdThis document compares the current YAZA source tree and runnable native API with Appendix H of the security blueprint. Appendix H is a target design, not a set of implemented guarantees. “Partial” means a named control exists in…
appendix-h-security-status.mdAuthor: Yahya Zakariya Project: YAZA Programming Language Edition: Living manuscript, 0.6 Status: Coding textbook in progress; implementation snapshot dated 28 October 2026 Audience: Complete beginners, then programmers learning…
tutorial/yaza-programming-language-book.mdLanguage-core progress estimate — 2026-10-27: about 35%. This is a manual estimate against the accepted general-purpose language design, not a percentage of source files or tests. The self-hosted compiler and core control-flow,…
runtime-capability-matrix.mdAPI work is the first product priority. Web, monolith, and mobile work starts after the API release gates below are met. “100% complete” means complete against a published, versioned API profile and its acceptance tests; it cannot…
api-completion-roadmap.mdcompiler/nativecli.yz is a YAZA-written, self-hosted compiler/CLI slice. It supports --version, --help, new, generate, db migrate, db status, audit --security, check, test, bench, build, and run. The security audit emits YAZA JSON…
native-cli-installer.mdVersion: 1.2 Reviewed against repository state: 2026-10-28 Scope: YAZA compiler and CLI, generated native programs, the API runtime, PostgreSQL client, local build/test workflow, and declared target status.
security/threat-model.mdWritten and created by Yahya Zakariya YAZA Programming Language (YAZA Lang)
architecture/yaza-architecture-book.mdMapping version: 1.0 Baseline: OWASP Top 10:2021, retained as a historical snapshot Reviewed against source tree: 2026-10-27 Status: Prototype control inventory; not a security certification
owasp-top-10-2021-mapping.mdStatus: Current-state mapping and proposed release checks; not an OWASP certification Reviewed against repository status: 2026-10-28 Related: Security assurance proposal, Appendix H status, YAZA threat model
security/owasp-api-security-2023-mapping.mdStatus: Integrated proposal; implementation and operational commitments are tracked separately Baseline review: 2026-10-28 Scope: YAZA compiler and CLI, generated C and native programs, API runtime, PostgreSQL clients, standard…
security/yaza-security-review-proposal.mdMapping version: 1.0 Baseline: OWASP Top 10:2025 Reviewed against source tree: 2026-10-28 Status: Prototype control inventory; not a security certification
security/owasp-top-10-2025-mapping.mdThe runtime-security workflow starts with six HTTP/JSON seeds generated by scripts/seed-http-fuzz-corpus.sh. That script also copies every .seed file in tests/fuzz-corpus/ into the temporary libFuzzer corpus. The deterministic…
fuzz-regression-workflow.mdyaza db snapshot [output.json] connects to the PostgreSQL database selected by DATABASEURL and writes a canonical catalog snapshot. The default path is yaza.schema.json. The connection uses the YAZA PostgreSQL v3 client and…
postgresql-schema-snapshot.mdYAZA supports an explicit defer cleanupcall(arguments) statement. It registers one direct function call in the current lexical C scope. Arguments are type-checked and evaluated once, from left to right, when the statement runs; the…
deferred-cleanup.mdStatus: Accepted Areas: Appendix G.1, G.3, G.5, G.6, G.10; Appendix H.4 Depends on: RFC 0002 for ownership and representation rules
rfcs/0001-core-types-and-errors.mdStatus: Accepted Areas: Appendix G.1, G.3; Appendix H.4, H.5, H.7 Depends on: RFC 0001 for value and error types
rfcs/0002-memory-ownership-and-unsafe.mdStatus: Accepted Areas: Appendix G.2, G.4; Appendix H.6, H.11, H.14, H.17
rfcs/0003-modules-packages-and-supply-chain.mdStatus: Accepted Areas: Appendix G.5–G.18; Appendix H.8, H.10, H.12 Depends on: RFCs 0001, 0002, and 0003
rfcs/0004-layered-api-and-postgresql.mdStatus: Accepted Areas: Appendix G.14, G.15, G.17, G.18; Appendix H.7, H.8 Depends on: RFCs 0001, 0002, and 0004
rfcs/0005-concurrency-and-http-runtime.mdStatus: Accepted Areas: Appendix G.7, G.12, G.18; Appendix H.8–H.13
rfcs/0006-secure-standard-library-and-crypto.mdStatus: Accepted Areas: Appendix G.16, G.18; Appendix H.1–H.3, H.6, H.14–H.18
rfcs/0007-diagnostics-testing-and-release-evidence.mdStatus: Accepted Areas: Appendix G.18–G.19; Appendix H.13 Depends on: RFCs 0001–0003 and 0006
rfcs/0008-cross-targets-linux-wasm-edge-mobile.mdThis 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…
rfcs/README.mdStatus: Draft proposal — awaiting owner review Proposed engine name: YAZA Atlas Scope: YAZA-owned geospatial kernel, map data pipeline, renderer, offline packs, and later search/routing services
proposals/yaza-atlas-maps-engine.mdStatus: Proposed; accepted by the project owner for proposal work, not yet implemented Product name recommendation: YAZA Base CLI surface: yaza db ... Engine process name: yazad (provisional)
proposals/yaza-base-sql-database.mdStatus: Draft proposal — module catalog and dependency direction for review Purpose: Plan a coherent collection of first-party packages for backend, web, mobile, data, maps, realtime, and deployment
proposals/yaza-ecosystem-module-roadmap.mdStatus: Accepted product direction — initial web starter foundation implemented; full system remains incomplete Scope: A YAZA-owned design language, component standard, web renderer, and future mobile renderer Decision: YAZA UI is…
proposals/yaza-ui-design-system.mdStatus: Accepted design direction — staged implementation in progress Scope: Standard-library design for data files, documents, media, statistics, and web applications Decision: Accepted by the project owner on 2026-10-24. Option A…
proposals/yaza-data-media-web-modules.mdStatus: Recommended architecture — implementation staged by API priority Priority: API completion; PostgreSQL first Implementation status: PostgreSQL protocol, transport, and CRUD foundations exist. Generated API builds use the…
proposals/yaza-database-drivers.mdProposals 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.
proposals/README.mdStatus: Accepted design direction — implementation pending (accepted by the project owner on 2026-10-24) Proposal name: YAZA Pulse Scope: Typed realtime sessions and a durable, partitioned publish/subscribe event broker for YAZA…
proposals/yaza-pulse-realtime-engine.mdStatus: Proposed draft plan for review by the project owner. This document is written to be folded into the API completion plan or an RFC; it is not an accepted decision. Its implementation notes were refreshed on 2026-10-27 to…
drafts/gate-a-implementation-plan.mdStatus: Proposed draft test plan for review. This document is written to be folded into the API completion plan (Gate B evidence) or an RFC; it is not an accepted decision and does not change implementation status.
drafts/postgresql-live-verification-plan.mdStatus: Proposed — draft for review by the project owner. Not accepted; nothing in this document changes implementation status. The exact numbers, examples, and diagnostics text are subject to revision before acceptance. Written to…
drafts/rfc-draft-small-syntax-decisions.mdTidak ada dokumen yang cocok. Coba kata kunci atau jenis lain.