platform architecture
Spine — the governed delivery loop
A request flows top-to-bottom — through comprehension and planning into an execution loop that pauses at human gates — and out as a reviewed PR.
Observability · Audit
A · Surfaces
CLI
cli.pyMCP plugin server
plugin/Web UI + REST API
registry/Terminal UI
tui/B · Intake & comprehension · deterministic, no-LLM
Intake
intake/Catalog / profile
catalog/Knowledge synthesis
knowledge/Product Knowledge Graph
pkg/ · the source of truthCode + docs → 7 node / 9 edge kinds, file:line-grounded, deterministic. A substrate the comprehension & delivery layers read from — not a peer box.
C · Planning
Planner
planner/GraphIR — the typed plan
ir/Registry
registry/🔒 GATE 1 · approve intentsapproval/
D · Governed execution loop
Runtime loop
runtime/perceive → plan → act → observeVerifier chain
runtime/schema · confidence · evidence · policyGateway
gateway/sandboxed tools + credsDurable execution
temporal/resumable across gate pausesE · SDLC delivery
SDLC pipeline31
sdlc/spec → codegen → tests → PRAgentic codegen
agentic/Code review
codereview/Personas
personas/🔒 GATE 2 · approve mergeapproval/
✓ Reviewed, CI-green Pull Request
F · Shared services · used across every layer
Core
core/MCP client
mcp/Storage
storage/Notify
notify/Evals
evals/Semantic spine
spine/ · gated Flow layer Human gate (lock · amber) Knowledge-graph substrate Optional · gated A request (the pulse)