Current decision: NO-GO for a production-qualified 1.0 language release. This is a usable developer preview with native binaries and functional backend and editor tooling. Passing the tests below establishes those tested behaviors; it does not prove secure operation for every program, workload or deployment.
Primary target selected for qualification: x64 Windows servers. Development verification uses Windows 11, Rust 1.89 and VS Code 1.141. Windows Server versions must be selected, exercised on clean hosts and recorded before declaring support.
| Gate | Current evidence / remaining work |
|---|---|
| Native compilation and diagnostics | Unit tests plus actual native compiler integration tests |
| REST behavior and persistence | Automated CRUD/auth/body/route tests, concurrent writes, restart persistence |
| Capability restrictions | Compilation failures for forbidden references/env/storage; runtime SQL escape-operation tests |
| Runaway-handler protection | Loop ticks, call-depth guards, request deadlines and SQLite progress cancellation; no OS guarantees |
| Editor integration | Packaged VSIX and LSP protocol tests; extension-host test provided, requires available VS Code |
| Clean Windows Server installation | OPEN: validate CRT prerequisites, permissions, clean artifact deployment and compiler installation |
| Service lifecycle | SCM hosting implemented; OPEN: real service installation, stop/restart/shutdown qualification and recovery on Windows Server |
| Hard isolation | Windows workers, committed-memory containment/restarts and CPU hard-cap configuration/readback tested on Windows 11; OPEN: CPU load measurements, target-server qualification, hardened permissions and independent review |
| HTTP ingress defenses | OPEN: integration with selected HTTPS proxy, slow headers/connections, rate limits and malformed-traffic corpus |
| Data operations | SQLite and MongoDB batch transactions implemented; SQLite backup/restore tested; OPEN: migration/version policy and Atlas backup/restore |
| Authentication/security | OPEN: independent review of capabilities, SQL/path checks and auth examples; identity integration and secret rotation exercises |
| Reliability/performance | OPEN: sustained load/soak results, memory/handle growth, overload recovery, p95/p99 latency and failure injection on target hardware |
| Observability | JSON request logs, request IDs, metrics and health/readiness implemented; OPEN: stable error taxonomy and operational qualification |
| Compiler robustness | Deterministic malformed-source corpus and source-depth checks; OPEN: coverage-guided fuzzing, larger conformance corpus and backend diagnostic mapping |
| Release/reproducibility | Lockfiles present; OPEN: offline dependency distribution, artifact signing, SBOM, audit/update process and reproducible build qualification |
| Language stability | OPEN: frozen semantics, compatibility/deprecation policy and versioned conformance suite |
| Editor completeness | Semantic references, unsaved import overlays, checked rename and signature help implemented; OPEN: incomplete-source behavior, type annotations and debugger |
Do not rename the current release “production ready” by removing this table. Each open gate needs implementation where appropriate and recorded evidence on the supported environment. Keep the status accurate when a gate is met.
Suggested next release sequence: stabilize request/storage semantics and data migrations; add Windows service integration; qualify CPU budgets and worker containment and operations on target servers; build the semantic editor/conformance corpus; then complete load/security/release audits before freezing a 1.0 contract.