Strata · Developer preview
What works.
What comes next.
We are opening the work while it is still experimental. Here is the difference between code that exists, behavior we have checked, and the journey we still need to finish.
Assessed · A dated snapshot, not a completion promise.
Read the capability tableA preview you can inspect.
This website explains the model and runs illustrative simulations. Studio is separate software you self-host. The development setup targets Linux with Node 22+ and HTTPS, your own Cloudflare Artifacts account and namespace, plus a separately installed Windows coding-agent runner. It is not a hosted Studio service or a one-click production kit.
The next workflow milestone: complete and qualify approved Release → saved Profile → Local Build after publication. Existing components and finite tests do not make that entire flow complete.
Implementation is one column.
Evidence is another.
- Implemented
- Code supports the stated, bounded contract.
- Tested
- The named local, synthetic or attended checks were performed.
- Next
- Unfinished work, with no delivery-date promise.
On a narrow screen, focus the table region and scroll horizontally. Row and column headings stay part of the table.
| Capability | Implementation | Tested / evidence boundary | Next / still missing | Source contract |
|---|---|---|---|---|
| Exact intent and reviewed baselines | Implemented | Finite local and synthetic workflows exercise owned Layers, composition, evidence and explicit approval gates. | Broaden supported profiles; qualify production use. | Implemented contract |
| Studio authoring and review | Implemented, opt-in | Synthetic browser/backend checks cover browsing, owned drafts and review actions; attended Save confirms a real agent-generated private draft. | Complete owner acceptance through an approved Release. | Finite first-project workflow |
| Windows Codex proposals | Implemented, bounded | Attended real provider proposal and explicit owner Save. Synthetic checks cover the integration contract. | Qualify each native host/version; other adapters require separate evidence. | Agent compatibility |
| Original-result recovery and Stop | Implemented, bounded | Real original-result recovery and a fresh Stop were demonstrated using an instrumented compiled runtime. Packaged bytes were checked separately. | Unattended operation and always-on runner availability are not qualified. | Connection lifecycle |
| Finite validation and approved Release | Implemented | Local/synthetic finite workflows exercise measured checks and separate approval gates. The attended saved draft has no accepted candidate or approved Release. | Close the full human-controlled Studio acceptance loop. | Release prerequisites |
| Saved Profiles → Local Build | Components implemented | Scoped synthetic persistence and build contracts exist. Complete end-to-end self-hosted acceptance is not established. | After publication: finish and qualify the integrated Profile → Build flow. | Local Build contract |
| Cloudflare and hybrid execution | Separate implemented path | Historical hybrid cloud success and candidate synthetic regressions are separate evidence. They do not demonstrate Studio browser completion. | Qualify each explicitly configured provider and deployment path. | Hybrid bridge contract |
| General synthesis and reconstruction | Planned / unproven | Finite profiles and supplied-proposal translation exist. There is no general independent-reconstruction result. | Broader profiles, semantic discovery and repeatable independent evaluations. | Profile boundaries |
This assessment uses product candidate 281d44e149ca772533409e77d6d72ccec60f248c. Source links target the product repository’s main branch; access or updated documents may remain unavailable while integration and publication are prepared. Private operational receipts are not published here. Synthetic success is not live provider conformance, independent review or production qualification.
Building in public
Small steps.
Visible boundaries.
- Prepare the public preview. Finish the publication boundary, installation guidance and distribution notices; keep README, site and roadmap aligned.
- Finish Profile → Build. Start from a genuinely approved Release, preserve exact profile and authority bindings, and qualify the complete self-hosted journey.
- Expand with evidence. Add profiles and supported environments, then measure reconstruction and agent collaboration without treating finite demonstrations as general proof.
Start with the local demoRead hosting prerequisitesRead the preview FAQ