Architecture wireframes

The system's architecture lives as an editable Figma/FigJam board, not a static picture — the design coworker maintains it through CRUD operations, styled with the same design tokens the sites themselves ship.

The practice

Three coworkers pair on every architecture diagram:

• Design owns the board: creates it via the official Figma MCP (generate_diagram, Mermaid → FigJam), reads it back (get_screenshot), updates it in place by fileKey, and records it in a wireframe-set ledger (plugins/cwc-design/wireframes.json) so boards are found, not regenerated. Retiring a board is operator-gated.
• Engineering supplies the system facts — which workers, crates, plugins, and API routes actually exist. Every box on a board is a verified real thing; a diagram with an invented box is documentation fraud in picture form.
• Data supplies warehouse-side facts where a diagram touches the DWH.

Boards use the family web tokens (workers/_shared/kit): panels #111 on #0a0a0a, group strokes by meaning — cyan #51c4ff for plugins, green #7bd88f for primitives, gold #e0b84e for identity, slate #93a5c4 for the fleet, amber #f4a73b for the operator. The Hardware Buddy's 8-token palette is a different system for a different surface and is never mixed in.

The current board

The full-system overview — twelve domain plugins + two specialized → identity and role directives (subagentroles.com, subagentidentities.com, subagentcode.com) → durable primitives → the 50-site fleet — was generated 2026-07-02 and is editable at:

figma.com/board/f3POlLrQzTL7JmDIbi7BX3

A diagram is dated data, not a timeless truth: the generation date travels with the board's ledger entry, and updates go to the same board by fileKey rather than spawning near-duplicates.

Why CRUD and not regenerate-every-time

The same reason the rest of this platform keeps durable rows instead of chat-transcript state: a board that isn't findable gets regenerated, and two divergent copies of "the architecture" are worse than none. Create once, read before updating, update in place, retire explicitly (gated).

Related

• Role taxonomy — what the board draws
• How it works
• Approval gates