docs: add architecture diagram#145
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Verified against actual source code and corrected: - Remove fictional CLASSIFY node (routing is done by WorkflowRouter) - Show Feature and Bug as separate graphs with correct node names - Fix Redis stream names (forge:events:jira, forge:events:github) - Fix metrics endpoint path (/metrics, not /api/v1/metrics) - Fix container task path (/task.json, not .forge/task.json) - Add Gemini as a supported LLM backend - Add missing nodes: local_review, update_documentation, setup/teardown_workspace, task_router, completion/aggregation Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ekuris-redhat
force-pushed
the
docs/architecture-diagram
branch
from
34a1cd9 to
a38f15c
Compare
StLuke
left a comment
StLuke
left a comment
There was a problem hiding this comment.
My 2 cents: it's hard to distinguish where are things running from the architecture diagram. Deep agents are in external systems with JIRA and GitHub, while running locally.
Also LLM backends seems to be on the bottom of the diagram the end path of architecture, while you might want to get a response from them to interact with. (Might be good to set path between LLM backends and Podman container.
Just my 2 cents (I definitely didnt spend enough time in the repo to assess if I'm wrong here :)
- Remove Deep Agents from External Systems (it's a library, not a service) - Show LLM Backends connected to both orchestrator and container - Clarify Deep Agents runs inside Podman containers - Add bidirectional LLM call arrows Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Lukas Svaty <StLuke@users.noreply.github.com>
| │ │ | ||
| │ Routes by Jira issue type: │ | ||
| │ Feature/Story --> FeatureWorkflow (StateGraph) │ | ||
| │ Bug --> BugWorkflow (StateGraph) │ |
There was a problem hiding this comment.
There is a task workflow now, so it should also be included
| │ │ create_pr │ │ │ │ | ||
| │ │ teardown_workspace │ └──────────────────────────────┘ │ | ||
| │ │──────────────────────────────│ │ | ||
| │ │ wait_for_ci_gate │ │ |
There was a problem hiding this comment.
wait_for_ci_gate will likely be removed following the implementation of #137. The diagram will need updating following it.
There was a problem hiding this comment.
give me an heads up once the PR 137 will be merged I will do the needed changes
3 participants
Summary
docs/architecture.mdwith system overview diagram, ticket lifecycle flows, and data flow summaryTest plan
🤖 Generated with Claude Code