docs: architecture diagram#1142
Conversation
📝 WalkthroughWalkthroughThis PR introduces two new developer-facing architecture documents explaining the ctrlplane orchestration system. The overview page illustrates the end-to-end flow from CLI version registration to job completion, while the workspace-engine guide details the core Postgres-backed controller orchestration. Navigation configuration is updated to surface these new pages under an "Architecture" tab. ChangesArchitecture Documentation
🎯 1 (Trivial) | ⏱️ ~3 minutes
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds a new "Architecture" docs tab with two pages — a system overview and a deep-dive into the workspace-engine — including Mermaid diagrams that explain how releases flow through the reconcile queue.
Changes:
- Register a new "Architecture" tab with a "System" group containing two pages in
docs/docs.json. - Add
docs/architecture/overview.mdxdescribing the high-level orchestration loop between web/api/engine/agents. - Add
docs/architecture/workspace-engine.mdxdescribing controllers, the release-flow chain, and thedesiredreleaseinternals.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/docs.json | Adds the Architecture tab and its two pages to the docs navigation. |
| docs/architecture/overview.mdx | New high-level system overview with a Mermaid flowchart. |
| docs/architecture/workspace-engine.mdx | New deep-dive on the workspace-engine controllers and release flow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/architecture/workspace-engine.mdx`:
- Line 8: Change the misspelled word "enqueueing" to "enqueuing" in the sentence
"and runs the matching controller. Each controller's output is enqueueing more"
so the line reads "... Each controller's output is enqueuing more" (search for
the phrase containing "enqueueing" in workspace-engine.mdx to locate the
occurrence).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 48a38f18-2817-47cb-8565-2a5198ff08a0
📒 Files selected for processing (3)
docs/architecture/overview.mdxdocs/architecture/workspace-engine.mdxdocs/docs.json
|
|
||
| The workspace-engine is the Go service that drives every release forward. It | ||
| polls a Postgres work queue (`reconcile_work_scope`), leases items by `kind`, | ||
| and runs the matching controller. Each controller's output is enqueueing more |
There was a problem hiding this comment.
Fix spelling at Line 8 (enqueueing → enqueuing).
This is a user-facing docs typo and should be corrected for consistency.
🧰 Tools
🪛 LanguageTool
[grammar] ~8-~8: Ensure spelling is correct
Context: ...controller. Each controller's output is enqueueing more work, so a single release moves th...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/architecture/workspace-engine.mdx` at line 8, Change the misspelled word
"enqueueing" to "enqueuing" in the sentence "and runs the matching controller.
Each controller's output is enqueueing more" so the line reads "... Each
controller's output is enqueuing more" (search for the phrase containing
"enqueueing" in workspace-engine.mdx to locate the occurrence).
Summary by CodeRabbit