Schematics
How KEEP is actually built
The same architecture described in prose on How KEEP Works and Merlin, here as diagrams — the actual boxes, arrows, and trust boundaries, not a simplified narrative. Every component is labeled Current, Planned, or Future; nothing built is drawn as if it were still theoretical, and nothing unbuilt is drawn as if it already shipped.
(Source: KEEP architecture documentation) (Source: Merlin architecture documentation)
Diagram Sets
Two schematic sets, nine diagrams total
Merlin's governance and decision model, Hub/Spoke system architecture, the Merlin layer stack, incident and signal intelligence, Spoke enrollment's root of trust, authentication and sign-in, and technician authorization and roles.
Open schematic →What's actually live today — routes, the LLM provider path, audit destinations — plus the proposed correlation/knowledge-engine pipeline, with an explicit findings section checking the diagram's own claims against the architecture docs.
Open schematic →Each schematic opens as its own page, outside this site's usual layout — that's deliberate, not a broken link. They carry their own legend, their own light/dark theme, and their own findings sections calling out exactly where a claim in the underlying architecture documentation didn't hold up under direct code inspection, corrected rather than smoothed over.