Highest zoom level. Helix as a black box surrounded by external actors and systems. No internals — just what touches it and how.
MCP / data
User interaction
File pipeline
Events
Extension layer
C4 LEVEL 2CONTAINERS
Containers — Major Deployable Units
One zoom in. Every runnable container or service in the Helix system — what technology it uses, what port it runs on, and how they wire together.
C4 LEVEL 3COMPONENTS
Components — Inside Helix Cortex API
Zooms into the FastAPI application itself. Every router, service layer, and how they delegate down to storage. This is what developers integrate against.
Entry / routers
Search / KG services
Write / Forge
Observer / events
★ = primary write entrypoint
FLOW VIEWWRITE PIPELINE
Data Flow — helix_file_write Unified Pipeline
What happens every time a file is written through Helix. Six atomic steps in sequence. This single tool call is what makes files searchable, versioned, and part of the knowledge graph.
LOOP VIEWSUPERLOOP
Superloop — The AI Memory Cycle
The temporal loop that makes Helix self-improving. Each session's output becomes the next session's input. MemBrain closes the loop at the Claude.ai layer. The system gets smarter by existing.
WHY IT'S A LOOP, NOT A PIPELINE
A pipeline has a start and end. The Superloop has no end — each session's output becomes the next session's input. MemBrain at step ② is what physically closes the loop back into Claude.ai before each message is sent.
WHAT MAKES IT SELF-IMPROVING
Every helix_file_write call (step ④) adds content to 3 search engines simultaneously. The more sessions that run, the richer the tier-1 context MemBrain can inject. The system accumulates intelligence by operating normally.
INFRA VIEWVPS TOPOLOGY
Infrastructure — VPS Topology
Physical deployment view. What runs on which server, which ports are exposed through Traefik, where data lives, and which containers are healthy vs pending setup.