changelog · roadmap
Built in waves, verified in public terms
Orvlet is built in waves. Each wave is built, independently re-verified, then committed after the local validation gate. This page is the public summary; detailed verification evidence stays with the development repository until the source export.
Recent waves
-
Editor-first workspace
A visible Code view with Files, Search, Changes, Terminal, Run and Preview; split layouts up to four groups in main and side areas; reply summaries and activity details as compact disclosures. Scoped real-app checks pass; broader split acceptance remains partial.
-
Native model coverage grows
Additional local checkpoints verified inside the Orvlet Engine with exact-output comparisons, offline runs and clean unload behavior. Most of the 2,000 tracked checkpoints remain not verified — the count is reported as-is, never rounded up.
-
Auto-review and privacy extras
Optional approval reviewer, encrypted transcript storage, a provider privacy filter, named permission profiles and a shell environment policy that keeps secret-looking variables out of agent commands by default.
-
Engine parity, images, live artifacts
Engine routes for tokenize, rerank and Responses; Stable Diffusion image generation verified with a small model; live sharing, Meetings, interactive answers, browser tools for the user and a VS Code companion. Several of these are unit-tested with real-app acceptance still open.
-
Standalone, local-first core
Vendor services removed; English-only interface; provider-neutral models with OS-backed credentials; approvals, sandbox and folder trust; macOS desktop and SSH remote workspaces.
What's next
- Real-world verification: cloud backends (Bedrock, Vertex), messaging channels, a live microphone, sleep/wake, Computer Use with real permissions, LAN sharing on a real network, a real phone, the VS Code extension in VS Code, and signed-build system integrations.
- Signed public release: complete packaged acceptance, notarization, and this site's download page gaining an actual verified artifact with checksums and provenance.
- Public source export: fresh-history Apache-2.0 repositories for the app and this website, with contribution guidance.
- Remaining gaps: the tracked Partial and Missing features, worked in the open once the export lands.
How to read our claims. “Verified in the app” means a real build was run. “Covered by tests” means exactly that — useful, but not the same thing. When the two scopes differ, we say so instead of equating a green gate with a working feature.