01 / Agentic Automation
- 72h
- From start to shipped
- Any
- Source change triggers a sync
The problem
Internal documentation was out of date the moment it was written. Keeping a wiki current meant a person noticing that something upstream had changed and copying it across by hand, and every downstream team needed the result in a different shape.
The approach
- 01
A self-updating wiki that watches Notion and the external repositories it draws from, and syncs automatically on any source change.
- 02
Requirement-aware distribution rather than a broadcast: each downstream consumer receives the content shaped to its own requirements.
- 03
Built with Claude Code and Claude Routines (.mjs scripting) as the primary development tools, not as assistants on the side.
- 04
Shipped end to end in a single 72-hour sprint.
- 05
Now building Halo Mirror, a multifamily automation pipeline on MCP connectors that applies the same requirement-aware distribution. It is in progress, not shipped.
Stack
This is the clearest example of coding agents as a production workflow rather than a demo: the system was built with them, end to end, in three days.