Notes on software a company can own.
What we learn mapping processes, writing contracts before code, and running software that stays governed after the first release.
-
Company brain AI hears the chat. Who writes down the rest?
Company brain AI can recall every thread. 4 other layers of company knowledge need writing down: a 5-layer model, survey numbers and a 10-decision test.
-
Claude Code context window full: what to do, what is lost
Claude Code context window full? A summary replaces your conversation. What survives, what is lost, and the 5 commands to use before it happens.
-
MEMORY.md vs CLAUDE.md vs AGENTS.md: which file does what
MEMORY.md vs CLAUDE.md is a question of who writes the file. What each one loads, when Claude Code reads AGENTS.md, and how to use all 3 without duplicates.
-
AI agent memory architecture: what to keep, and where
AI agent memory architecture in practice: the 4 kinds of memory my Claude Code agents use, where I keep each one, and what breaks when they mix.
-
Multi-agent orchestration with Claude Code: my setup
Multi-agent orchestration without a framework: how I split marketing work across Claude Code agents that share one memory in Markdown files, and what broke.
Bring the process, not the pitch.
A 30-minute fit call on the one process your team keeps working around. If standard software is the better answer, we say so.