Visual Documentation

The Engine in diagrams. A visual tour for anyone who wants the shape of a subsystem before the prose — developer, evaluator, or operator. Each diagram gets a short caption and a link to the section that explains it in depth; the diagrams carry the load.

The tour

Read top to bottom for a guided pass from the static structure down to a running, deployed system:

1. Architecture — the components and how they connect; the tool-router capability map.
2. Concepts — the four topologies, one shape at a time; how Template, Team, Agent, and Project relate; how a template becomes a project.
3. Request Flow — a message through the ReAct loop: the run sequence, the MCP session lifecycle, push-dispatched delegation, and how the model for a turn is chosen.
4. Permissions — the three-layer permission model as a funnel: connection → capability → runtime.
5. Deployment — the single-host topology, the integration peers, configuration precedence, and the self-managing/operator-owned split.

Reading the diagrams

• Copper nodes are the primary actor or the decisive enforcement point (the server, the router, the supervisor, the runtime gate).
• Sage nodes are components and workers.
• Tan nodes are external systems and edges — the user, the browser, a template file, a container.

Every diagram here also lives in, or is verified against, a Developer section — follow the cross-link under each for the full explanation. Nothing in this set is new fact; it is the same Engine, drawn.