How gruizv/agenticcollaborationsystem works
Project Type and Purpose
• This is an “agentic collaboration” framework rather than a traditional web app or microservice.
• It provides a file-based memory layer for multiple Roo agents (Orchestrator, Architect, Code, Debug, Ask) to coordinate over a shared filesystem.
• The pj_directory holds the actual user project code and tests; roo_state is the append-only state store; SOPFs holds the prompt footers per mode.
Main Components
a. External User
b. Agents
• Orchestrator
• Architect
• Code
• Debug
• Ask
c. Shared Memory Layer
• roo_state/project_state.md (central “database”)
• roo_state/.roo-config.yaml (mode metadata)
• roo_state/[Mode]/mode_log.md (per-agent logs)
d. Project Source & Tests
• pj_directory/src/
• pj_directory/tests/tests_log.md
e. SOPF Directory
• SOPFs/[Mode] SOPF.md
Relationships & Data Flows
• User → Orchestrator: initial prompt, project goals.
• Agents → Orchestrator: “Work Complete” callbacks.
• All Agents ↔ Shared Memory:
• Read project_state.md then their own mode_log.md (Bootstrapping).
• Write to their mode_log.md + append orchestrator summary to project_state.md (Execution).
• Code & Debug additionally append to tests_log.md when tests are created/fixed.
• Ask mode: occasionally reads from and writes to project_state.md; provides explanations to User and Orchestrator.
Architectural Patterns & Principles
• “File-based event sourcing”: append-only logs for auditability.
• “Single source of truth”: project_state.md as central document.
• “Role separation”: each agent has isolated local memory but shared coordination via Orchestrator.
• “Bootstrap–Reconcile–Execute” cycle per agent.
Technologies & Artifacts
• Markdown/YAML files as “storage” nodes.
• .roo-config.yaml as a small config “service.”
• pj_directory as standard code/test folder.
• SOPFs as prompt templates (show them as static assets).