ONE ENGINEER · 19 SERVERS · 270+ TOOLS
An AI engineering platform built on Cloudflare, by a Cloudflare engineer. Every tool is a typed MCP server, every server composes through a shared protocol, and every page on this site — including this one — was rendered by the system it describes.
17 custom-built, 1 remote gateway, 1 third-party integration.
One function per file. Auto-discovered at startup. Typed inputs and outputs.
Platform · Writing · Orchestration · Visual · Domain
Native TypeScript. No build step. Sub-second server startup.
MCP servers compose because they share a protocol. The output of one server — a resolved path, a committed SHA, a rendered SVG — becomes the input to the next. No integration code. No adapters. Just typed tools calling typed tools.
scout resolves a repo hint to a working directory. git-ops takes that path and commits. Two servers, one protocol, zero glue code.
chromata resolves a color scheme to RGB values. xhtml-tools compiles a page spec into styled XHTML. wiki publishes to Confluence. gutenberg screenshots the result.
flowbot enforces phase constraints on tool access. roost coordinates parallel sessions. grounder tracks session learnings across conversations. The governance chain governs itself.
Five categories. Each server owns a domain and exposes typed tools through MCP. Platform servers manage workspace and code. Writing servers author and publish content. Orchestration servers coordinate multi-step workflows. Visual servers handle color, diagrams, and rendering. Domain servers connect to production systems.
Workspace management. Resolves repo hints to paths, manages git worktrees, handles all file operations. The only source of truth for where code lives.
Git primitives. Takes a path from scout and executes git operations. Commit categorization, MR lifecycle, branch management.
Configuration management for the OpenCode IDE. Manages MCP server registration, agent definitions, permission rules, and plugin wiring.
Server factory. Scaffolds new MCP servers with typed tool definitions, test harnesses, and publication pipelines.
Cross-server utilities. Shared TypeScript helpers, type definitions, and testing infrastructure used by all custom servers.
Confluence integration. Publishes compiled XHTML, fetches pages, edits in-place via DOM operations, searches content, screenshots results.
Page spec compiler. Transforms YAML page specs into Confluence storage-format XHTML. 20+ block types, scheme-aware coloring, structural validation.
Diagram engine. Ten structural forms rendered as budget-aware SVGs. Measures labels, allocates space, degrades gracefully. No scaling artifacts.
Color system. 21 OKLCH hue families × 11 shades, gamut-mapped to sRGB. Schemes, semantic roles, five color distribution functions.
Workflow engine. Phase-based tool scoping — each phase narrows available tools and directs attention through signals. The structural safety model.
Session coordination. Tracks parallel AI sessions, detects file conflicts, manages advisory path claims. Prevents sessions from stepping on each other.
Session analytics and memory. Records corrections, preferences, and workflow discoveries that persist across conversations. Usage trends and cost tracking.
Type system. Semantic type annotations across all servers. Tracks which tools produce which types and which tools consume them. The composition backbone.
HTML5 renderer. Compiles YAML page specs into standalone HTML documents with Tailwind styling. The engine that built this site.
What changes when AI handles the mechanical parts of engineering? From the foundational observation through methodology and practice to a formal argument for structural safety.
OKLCH color science, dark surface hierarchy, ten diagram forms, six visual principles. The constraints that ensure every page is legible, consistent, and beautiful.
The platform applied to Cloudflare's billing domain. Seam maps named the coupling. State machines formalized the lifecycle. The tooling made the analysis possible.
Every server was built by AI — through the servers on this page. Every page was rendered by gutenberg — the system described above. You're reading the proof.