v0.4.0 Stable¶
This is the canonical public release page for the stable minor release that introduces Skylattice's hosted web control-plane foundation.
What This Release Proves¶
- Skylattice now has a real hosted control-plane product surface instead of only a docs site plus local CLI/runtime
- the new web layer still keeps execution, memory, and governance local-first
- the repository can now show pairing, command history, command drill-down, device management, and approval reminders as first-class product surfaces
What Works Today¶
skylattice doctor- governed
task-agentruns with deterministic edit modes, reviewed memory context, and recovery-aware GitHub collaboration sync skylattice memory ...review, search, export, and rollback flowstechnology-radarruns with GitHub/GitLab discovery configuration, provider-tagged evidence, and bounded promotion metadataskylattice web status,web pair, andweb connector ...- hosted web workspaces for dashboard, tasks, radar, memory, commands, devices, approvals, and connect flows
- public proof artifacts and Pages landing pages for cold visitors
Verify It¶
Why This Stable Minor Matters¶
v0.3.1 closed the current Phase 5 operational-closure loop. v0.4.0 changes the product shape: Skylattice now has a hosted web control plane that can represent the system like a product while still leaving execution local and governed.
Known Limits¶
- there is not yet a public hosted deployment URL for the web app in this repository alone
- the most practical first entry is still local:
npm run web:dev - the public deployment contract now lives in
docs/ops/hosted-alpha-runbook.md, but deploying it still requires Vercel, Neon, and GitHub OAuth configuration outside the repo - task execution remains text-native rather than AST-aware
- meaningful task planning still depends on
OPENAI_API_KEY - the project is still early if you need a polished multi-user hosted platform