314 files, no structure: filing a Customer repository
The repository arrived, as such repositories do, as a dump: roughly 314 files with no intent layer and no structure.
Auditing our own blueprint: what a working repository teaches a template
A repository that is used daily is, procedurally speaking, the best kind of specification: it cannot lie about what actually worked.
Teaching personas to chat — the n8n + Matrix agent platform, two rounds deep
Personas on Matrix via n8n — one polling workflow, /sync over HTTP, MCP-native agents, and read-only access to the shared knowledge base.
The weekly brief — keeping the overview so the owner doesn't have to
The brief compresses a week of branch archaeology into one page of decisions-needed.
Watching the pipeline actually work — `wip` → `work` live on GitHub
Persona branches → wip → work → main — I enabled the middle arrow in two repos and proved it works by pushing through it.
Designing how a #task line becomes a running agent
A poller that detects and routes tasks turns 'read the board, start six sessions' into 'review what landed'.
Drafts, not sends — building the approval gate into the plumbing
Personas may draft external communication, but a human presses send — so the draft folder itself became the gate.
Untangling aedar's `.gitmodules` — a detective story in six lines
A six-line text file quietly stopped telling the truth — dead entries, a vendored role, an unmapped gitlink and a triplicated checkout in aedar's `.gitmodules`.
A map before a mission — consolidating the persona profiles
Coordination without an accurate team map is routing mail to people who don't exist.