Five planes, each resting on the one below it.
Core is the single source of truth. If a capability cannot express its output as a change to Core, it does not belong in the platform.
- Model
- Typed graph with provenance on every node and edge
- Language
- Plugin analyzers only. Everything above the model layer is language-neutral
- Deployment
- Bring your own cloud, on premises, or air gapped
The stack, top to bottom.
Each plane reads only from the plane beneath it and writes back to Core. The dependency direction is what keeps the model honest as the product grows.
Structure tells you what could happen. Runtime tells you what does.
Neither source is sufficient alone, and the interesting facts live in the intersection. Merging them is where a static analyzer and an observability tool each stop, and where this platform starts.
| Stratum | Source | Recoverable automatically |
|---|---|---|
| Surface | Files, dependencies, configuration, build | Yes |
| Structure | Call graph, schema, job graph, API surface | Yes |
| Semantics | Business rules, intent, the reason a thing exists | Partly. The rest is asked, never assumed |
| Runtime | Traces, hot paths, real inputs, failures | Yes, given instrumentation |
Where to go next.
Each capability has its own page, in the order the chain runs.
Evidence and the model
Ten connector families, degraded operation as the normal case, and the typed graph they all reconcile into.
F3Clarification
Gap detection, question synthesis, clustering, routing, escalation, blocking, and the designed experiment as an unblock path.
F4 to F7Delivery
The board of evidence states, context envelopes, agent dispatch, the cloud workspace, and merge from the dashboard.
F8Verification
Characterization tests captured from production, then differential replay with every difference ruled on by a named person.
F9Decisions
Migration forks presented with real tradeoffs, recommended with reasoning, and propagated as binding constraints.
DeploymentSecurity and deployment
Bring your own cloud from day one, redaction at the ingestion boundary, and a complete audit trail from evidence to merged commit.
What gets built, and what gets wrapped.
The moat is Core, the envelopes, the board, the decisions and the verification loop. Everything else is someone else's solved problem.
| Layer | Approach |
|---|---|
| Editor | An existing open-source browser editor server. Do not fork an editor. |
| Agent runtime | An existing open-source agent SDK with remote execution. Do not build an agent loop. |
| Sandbox | Hardware-isolated microVMs, self-operated. This is where reliability and cost are won or lost. |
| Source control and CI | The customer's existing host, through its API. Never rebuild it. |
| Static analysis | Existing parser and query infrastructure per language. Wrap it, do not rewrite it. |
| Telemetry | OpenTelemetry as the primary path, vendor APIs as adapters. |
| Core, envelopes, board, decisions, verification | Built in house. This is the entire moat. |