5 posts tagged workflow-atlas. ← Back to all posts
A topical roll-up of what shipped across the robot-md / OpenCastor ecosystem, the PlatAtlas / mcp-tape / mcp-replay family, and Heat Compass between January and 2026-05-19. Tables of versions, dates, and PR / release pointers. First dedicated coverage of Heat Compass on this site.
Agents arrive at each session without persistent state. Externalization mechanisms differ in what they capture: intent, declaration, structure, execution. Treating them as one bucket obscures the architectural choice in each. This post separates the four artifacts produced by the work shipped in 2026.
Two distinct product families ship from this account in 2026. They share no source code, no authentication, no brand, and no roadmap. They share an operator. This post documents their structural shape, their repository topology, and the resolution rule between them.
How my planning stack across the OpenCastor ecosystem — CLAUDE.md, MEMORY, spec/plan docs, status files — kept hitting the same ceiling, and what changed when Dave Jeffery posted a prompt about a single-page HTML + JSON workflow visualizer. The result is workflow-atlas, a Claude Code plugin that sits next to CLAUDE.md as the graphical layer over the textual context Claude already reads.
A few hours after writing about workflow-atlas as a context layer for Claude, I shipped the execution-layer companion. mcp-tape records every MCP JSON-RPC call your agent makes; mcpreplay.dev lets you read what happened. Open source, MIT, alpha.