Team memory

Within a goal, each role keeps one conversation: the developer goes from plan to tasks to fixes and still knows what it did and why, and the reviewer knows what it already pointed out. When that conversation gets too full, the agent summarizes it (compacting). A new goal starts with new conversations.

The roles don't talk to each other. That's why the team writes down everything another role needs, in the .coodoo/ folder in your project. This way the developer reads what the researcher found, and the reviewer knows what the plan was.

On the dashboard, Shared knowledge has shortcuts to the most important files.

The files

File	What's in it
research.md	The researcher's findings
design.md and design/	The design: screens, text, icons
technical.md	The technical design
plan.json	The plan with the tasks
notes.md	Handover notes between the agents
reviews/	The reviewer's verdict per task
security.json	What the app does that needs care, the risks and the safe choices
needs.json	Which programs the work needs
run.json	How the app starts
run-check/	The report and screenshots from the app check
next-goal.json	The idea for the next goal (with Keep going)
commit-msg.txt	The developer's commit message
state.json	The queue and the history of the goals
pause.json	A saved pause
logs/	The log (run.log) and the data for the statistics
versions.json	The version numbers of your parts

Outside git

Except for versions.json, the team memory is not in git. That way branches don't clash over it and no working material ends up in your repository. The files simply stay on your computer.

What's stored elsewhere

Some things aren't in your project but in Coodoo's own folder: the lessons and the Project map, the chat conversations, the release history, the Failsafes log, the price list for the statistics and the Requirements that Coodoo installed.

Tip: You can read the files yourself in the Project panel. Better not to change them while the autopilot is working.