X-BEIdeas · experiments · demos

Domain context for AI — E2 beside the architecture graph

Architecture docs as the API of the AI conversation; the domain model as the business API. How .storm.json and AGM fit together — together or separately.

July 22, 2026

E2AGMContext

Agents in enterprise work rarely fail because the model is “too small.” More often there’s no structured context: what may be built in the business sense, and how the system is cut architecturally. Chat prompts and whiteboard photos leave a gap.

AGM is my take on the architecture side: repo-local Markdown link graph, blueprint.md, graph traversal.

E2 is the domain side: modeling on a board, export as schema-valid `.storm.json`.

They’re complementary. Use one or both. The bridge lives under Compose.

← all notes