Skip to content

docs: clarify concurrent consensus protocol details [doc-updater] #1039

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jwbron merged 2 commits into from
Mar 12, 2026
Merged

docs: clarify concurrent consensus protocol details [doc-updater] #1039

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ad93aa
docs: document consensus phase completion details for concurrent mode
jwbron Mar 12, 2026
bb9c8e4
docs: break long consensus protocol lines into sub-bullets
egg-reviewer[bot] Mar 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/guides/sdlc-pipeline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1362,8 +1362,13 @@ Phase completion in concurrent mode uses a consensus-based approach:
1. Each agent works independently on its tasks
2. When an agent completes its work, it signals `READY`
3. Phase completes when **all** agents signal `READY`
- The orchestrator polls every 5 seconds and stops containers immediately on consensus
4. Any agent can object (signal `OBJECTING`) to block completion
5. Timeout triggers HITL escalation
- A HITL decision is created with options: **Override objections**, **Wait for resolution**, **Abort phase**
5. Timeout (`consensus_timeout_minutes`, default 30) triggers HITL escalation
- Options: **Continue waiting**, **Accept current state**, **Abort phase**
- Phase falls back to exit-code-based completion while awaiting the decision
6. If all containers exit before consensus, the phase completes based on container exit codes (same as non-concurrent mode)

**Readiness states**:

Expand Down
Loading