Source intake
Brings project material into structured, provenance-aware records instead of loose folders.
Architecture
A modular spine for app development with AI.
The public view is intentionally high level: enough for technical evaluation, not enough to expose internal mechanics. Two planes — data and control — reinforce each other.
The spine
Nine modules, one coherent spine.
A cool data plane carries knowledge; a warmer control plane oversees it. On the diagram, hover or focus a module to trace its connections; every module is also listed below.
The modules
Grouped by the work they do.
Data plane
Knowledge foundation
Defines shared contracts for artifacts, source references, retrieval, and refusals. Promoted as the canonical first-module baseline.
Retrieval system
Supplies task-specific context without exposing an open-ended raw query surface.
Tool gateway
Scopes AI access to approved project capabilities, with masked status instead of broad permissions.
Control plane
Proof & validation
Confirms that work has evidence, boundaries, verification, and a clean handoff before it can be accepted.
Governance & gates
Protected paths, owner approval, staged arming, and signing keep authority explicit.
Agent role injection
Keeps AI agent behavior inside controlled boundaries rather than open-ended autonomy.
Operations & worker system
Manages bounded work execution, failure handling, and handoffs between runs.
Operator cockpit
Presents status, evidence, approvals, and next actions to the human operator.
Follow a request
How one task moves through the spine.
A request enters the data plane: intake records its provenance, the knowledge foundation frames it, and retrieval supplies only the context the task needs. The tool gateway scopes any capability the agent may touch.
The control plane stays in charge throughout: proof and validation check the work, governance gates hold authority, agent roles bound behavior, operations manage execution, and the cockpit puts the decision in front of the operator. Nothing crosses a plane without passing its checks.
intake → recorded · provenance kept
knowledge → framed against contracts
retrieval → scoped context only
gateway → capability permissioned
proof → evidence required
cockpit → operator decision
handoff → preserved as memory
Public-safe by design
High-level on purpose.
This view shows the shape of the system, not its internals. Exact topology, protected paths, role mechanics, configuration values, and trust-root details stay private. That is the point: enough to evaluate fit, not enough to expose the build.
Next step
Want the technical walkthrough?
We can go deeper on the spine in a discussion-based session.