01 Architecture
Neutral at the seams. Opinionated at the core.
The system is designed so that no model, tool, or cloud owns your work — while running, today, on a concrete stack: compilers and execution on the Claude API, state in a durable store, every run receipted.
02 System diagram
How the pieces fit.
* Browser/computer execution stays gated until safely implemented. Diagram is a concept illustration of the architecture.
03 Layers
Each layer does one job.
Work State Alpha
The durable record: goals, constraints, decisions, artifacts, accepted and rejected outputs, pending actions, provenance. Versioned like code. Everything downstream reads from it; everything upstream writes to it.
Context Compiler Alpha
Decides what matters now: relevant history, files, prior decisions, skills. The antidote to stuffing entire chat logs into every prompt — and to forgetting the decision from last Tuesday.
Work Compiler Alpha · on Claude
Turns goals into inspectable plans — steps, dependencies, acceptance criteria, budgets, approval gates — using the Claude API for the reasoning. You review the plan before sensitive steps execute.
Provider adapters Claude live
Clean boundaries per provider: Claude today; OpenAI-compatible and Gemini in progress; local models planned. Routing can be manual or automatic with explanations. Vendor logic never leaks into your work.
Execution Ledger Alpha
Every real execution writes a receipt: provider, model, attempts, latency, tokens, cost, evaluation status. The ledger already tracks Claude API usage to the cent.
Evaluation Alpha
Deterministic checks, structured validation, human review. A 200 from the API is not a success — meeting the acceptance criteria is.
Recompiler Planned
Compares strategies on measured evidence — cost, latency, quality, corrective effort — and recommends migration, no migration, or further review. Never invents numbers.
04 Neutrality, concretely
What “vendor-neutral” actually means here.
Three enforceable properties, not a slogan:
1 · State outlives providers
Your Work State is provider-agnostic data. If Claude disappeared tomorrow, your goals, decisions, and artifacts remain — re-routable, not stranded.
2 · Adapters are boundaries
Each provider integration is a contained adapter with a stable interface. Adding Gemini doesn’t touch the compiler; swapping models doesn’t touch your plans.
3 · Costs are comparable
The ledger records every provider in the same units — tokens, latency, dollars, acceptance. Neutrality you can audit beats neutrality you have to trust.
And the honest counterweight: today the deepest integration is Claude — compiler, execution, and ledger all run on the Claude API. Neutrality is the architecture; Claude is the practice. We’re an independent product built on the Claude API, not affiliated with or endorsed by Anthropic.
Built for people who read architecture pages.
If this page made sense to you, you’re who the alpha is for. Request access and tell us what you’d run through it.