Roadmap
RAIQL development is moving from runnable generation toward verified, portable and extensible software delivery. Roadmap items are planned direction, not promises of current capability.
0.11 — Dependency & security hardening · current
Exact generated dependency baselines, raiql lock, lockfile hashing, raiql audit, Node/npm engine policy, security manifests and reproducible install behavior.
0.12 — OpenAPI & typed clients
Generate OpenAPI contracts from RAIQL APIs plus typed TypeScript clients so the declared application surface can be consumed outside the generated UI.
0.13 — Multi-tenant SaaS
Add tenant-aware identity, tenant ownership and tenant-scoped authorization suitable for B2B SaaS products.
0.14 — Events & background work
Introduce declarative events, jobs and queue intent with an executable first adapter rather than embedding framework-specific worker code in the language.
0.15 — AI-assisted requirements
Add an optional AI planning layer that translates natural-language requirements into reviewable RAIQL source. The deterministic compiler remains the execution authority.
0.16 — Deployment adapters
Expand deployment intent into production adapters for Docker Compose, Kubernetes and selected cloud targets with environment-safe configuration.
0.17 — Observability
Generate health checks, structured logs, metrics and trace hooks from application requirements.
0.18 — API and mobile targets
Promote TYPE API and TYPE MOBILE from contract-only targets into runnable generation paths.
0.19 — Extension model
Define a stable generator/plugin interface so third-party targets can consume the same RAIQL IR without modifying the language core.
1.0 — Stable language line
Freeze the first stable grammar and IR contract, publish a formal compatibility policy, ship the CLI through a durable package channel and make the core toolchain suitable for production adoption.