Documentation channel: current development main at compiler checkpoint 1d7e15e. The latest tagged release is v0.0.3; pages identify APIs that are not yet released.
Implementation status
This website describes current development APIs at compiler checkpoint 1d7e15e, which supersedes the P9 checkpoint d9e6c47. The latest tagged release is v0.0.3. Installation commands install the latest tagged release; APIs marked current-main or unreleased require a compiler built from development main.
Stable release and development
| Surface | Latest release v0.0.3 | Current main |
|---|---|---|
| Language, ownership, checked errors, packages, CLI/LSP | Available | Available |
| HTTP server, TLS, SQLite, buffered outbound HTTP | Available at the v0.0.3 contract | Expanded and hardened |
bytes, Base64/Base64url, crypto | Not released | Available |
| Outbound HTTP streaming and cancellation | Not released | Available |
| Streaming server requests/responses, persistence, helpers, ranges, NDJSON | Not released | Available |
| WebSocket server | Not released | Available |
| WebSocket-to-PTY sessions | Not released | Certified as application-level composition; no built-in bridge |
| Hardened process ownership and cancellable pipes | Earlier process API only | Available |
| PTY | Not released | Linux, macOS, and Windows ConPTY |
| Windows ConPTY | Not available | Available on Windows 10 1809 / Server 2019 or newer |
Current-main backend capability
| Capability | Runtime/compiler | Website |
|---|---|---|
| Secure random, SHA-256, HMAC-SHA-256, constant-time compare | Yes | Crypto |
| Strict Base64 and unpadded Base64url | Yes | Crypto |
| Outbound arbitrary methods, binary bodies, limits, redirects, custom CA | Yes | HTTP client |
| Outbound streaming upload/download, async, cancellation | Yes | HTTP client |
| Explicit client certificates, proxy options, Unix sockets | No | Documented limitations |
| Strict HTTP server, TLS, streaming, persistence, files, NDJSON | Yes | HTTP server |
| WebSocket server, subprotocols, messages, limits | Yes | WebSockets |
| Concurrent WebSocket read/write and PTY composition | Yes | WebSockets and Pseudo-terminals |
| Process cancellation, Unicode Windows spawn, tree ownership | Yes | Processes |
| PTY read/write, resize, controls, cancellation, cleanup | POSIX and Windows ConPTY | Pseudo-terminals |
| Windows ConPTY | Yes | Native implementation and executable lifecycle certification |
Platform certification
The compiler and generated C++ at 1d7e15e are certified on Linux x64 with GCC and Clang, Linux ARM64 with GCC, macOS ARM64 with AppleClang, and Windows x64 with MSVC. The independent regression suite is green against that exact SHA on Linux, macOS, and Windows. PTY behavior executes on all three operating systems; P9 added Windows ConPTY lifecycle certification, and P10 adds cross-platform WebSocket-to-PTY composition, full-duplex transport, stress, backpressure, shutdown, and resource certification.
Current positioning
Current main has concrete building blocks for serious native backend and full-stack work: HTTP/TLS servers, strict request framing, streaming bodies, persistence, NDJSON, outbound HTTP, cancellation, crypto, SQLite, full-duplex server WebSockets, subprocesses, concurrency, cross-platform PTYs, and application-owned WebSocket terminal sessions. These capabilities have focused compiler, protocol, lifecycle, resource, and cross-platform certification. The project does not yet label the complete backend/runtime stack production-grade; broader production certification remains later campaign work.
Still deferred
HTTP/2, ACME/certificate automation, reverse-proxy trust automation, outbound WebSocket clients, WebSocket extensions such as permessage-deflate, a built-in WebSocket-to-PTY bridge or terminal protocol, authentication/session frameworks, and a centralized package registry remain unimplemented or deferred.