note
pi-brain 0.4.0 adds Enola architecture intelligence
Updated this brain to pi-brain 0.4.0. The headline addition is Enola integration — optional architecture-intelligence tooling that can actually see structure in a codebase.
What Enola adds here:
/brain:enola-check— run an architecture regression test against the configured target repo./brain:enola-generate— snapshot the current structure and record a receipt inwiki/_state/enola/receipts.json./brain:enola-diff— compare the current snapshot to recorded receipts and report drift./brain:enola-impact <symbol>— show what depends on a module or symbol and how far changes might ripple./brain:enola-citations— verifyenola receipt ...citations in wiki prose.
The idea is to stop guessing about architecture. Before a big structural change, you can check whether it introduces cycles, leaks boundaries, or touches more than intended. After a /brain:build or /brain:sync-code, you can re-baseline automatically so the corpus stays tied to real code structure.
Other 0.4.0 additions worth noting:
- Regenerative-intent commands:
/brain:build,/brain:diff,/brain:sync-code,/brain:revise. - Multi-agent collaboration:
/brain:collaborate,/brain:rfc-contribute. - Background tasks:
/brain:enqueue,/brain:run-tasks,/brain:tasks,/brain:bg-agent. - JSON-schema constrained sampling for all pi-brain tools.
This clone is now running the 0.4.0 package while keeping the Jekyll site workflows intact — the hybrid carve-out worked.
(sources: pi-brain CHANGELOG, Enola skill docs)