/**
* Multica architecture diagram for §1.2 "How Multica Works".
*
* Boundary-style layout: one large panel for "Your side" (where all the
* interesting stuff happens — code, keys, compute), one smaller panel for
* "Multica" (metadata store and coordinator). The asymmetric sizes and the
* brand-tinted left panel visually argue Multica's core thesis: AI runs on
* your machine, not ours.
*
* No SVG arrows. Relationships are carried by the layout itself — client
* side vs. server side is the universal mental model, readers don't need
* arrows to understand it.
*/
export function ArchitectureDiagram() {
return (
{/* Desktop: asymmetric two-panel with connector */}
{/* Mobile: stacked */}
);
}
function YourSide() {
return (
Your side
{/* Client surfaces */}
{/* Horizontal separator */}
{/* Daemon + local tools */}
Daemon
Polls work from Multica. Invokes local AI coding tools:
Claude Code
Codex
Cursor
Copilot
+ 6 more
{/* Tagline */}
Your code.
·
Your keys.
·
Your CPU.
);
}
function MulticaSide() {
return (
Multica
Server
Cloud or self-hosted
Workspaces
Issues & tasks
Agent definitions
Realtime (WebSocket)
No AI execution here.
);
}
function Connector({ horizontal }: { horizontal: boolean }) {
if (horizontal) {
return (
⇄
);
}
return (
⇅
);
}
function SectionLabel({ children }: { children: React.ReactNode }) {
return (
{children}
);
}
function Pill({
children,
muted = false,
}: {
children: React.ReactNode;
muted?: boolean;
}) {
return (
{children}
);
}