Skip to content

Swarm stays opt-in; §1a propose-trigger for 3+ independent units #547

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
pftg merged 1 commit into from
Aug 21, 2026
Merged

Swarm stays opt-in; §1a propose-trigger for 3+ independent units #547

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 7 additions & 2 deletions docs/workflows/autonomous-delivery-prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,8 +100,13 @@ starts before it:
binaries/baselines do not count; docs-only work may batch bigger). A
sprint whose code diff would exceed the cap splits into sequential PRs:
merge N before opening N+1.
- *swarm scale*: only on explicit request — `ruflo-swarm`, workers in
worktrees (committing agents get isolation).
- *swarm scale*: NOT the default (decided 2026-08-21 — the 2025 hive era
produced the incidents today's rules prevent; sequential author/verifier
caught every defect the same day swarm-by-default was considered). When
a sprint contains 3+ independent same-shaped units (batch posts,
per-surface audits), PROPOSE swarm in the triage verdict; it activates
only on explicit request — `ruflo-swarm`, workers in worktrees
(committing agents get isolation).
5. **The contract — non-negotiable regardless of orchestration shape**:
feature branch + PR, never master, PR ≤ ~500 changed CODE lines
(docs/logs exempt) · rebase when master moves, never merge it in (tag a
Expand Down