update-overview

Automatically generating mermaid diagrams from project specs requires reading lodged spec artefacts like exploration.md, plan.md, and tasks.md. This process regenerates Feature Mindmap, Architecture, User Journey, and Data Model visuals directly from those lodged files to capture the cumulative project state.

A living project overview is an overall.md file reflecting current work through four mermaid diagrams. It stays updated by automatically regenerating its visuals whenever new specs are lodged into the .powerball/lodge directory, reducing manual maintenance.

Yes, you can regenerate a single architecture diagram instead of the full project overview. The process supports targeted regeneration for a specific lodged spec, allowing you to update individual visuals without regenerating all four diagrams.

Yes, you need spec artefacts in .powerball/lodge to update the overview. The process reads lodged exploration.md, plan.md, and tasks.md files directly from this directory to build and update the Feature Mindmap, Architecture, User Journey, and ER diagrams.

The best way to maintain an ER diagram for an evolving data model is to automate regeneration from lodged specs. By reading tasks.md and plan.md artefacts, the system updates the Data Model ER diagram automatically, ensuring it reflects current decisions without manual editing.

Your project overview diagram is not reflecting recent spec changes because the update process must be triggered to read newly lodged specs. Running the update process regenerates all four diagrams from the current exploration.md, plan.md, and tasks.md files to capture the latest cumulative state.