Proof over promises. Lanes over chaos.
We prefer inspectable work over vague claims: verified artifacts, closeouts, and live surfaces people can click.
Plain-language note
"Swarm", "fleet", and "operator" are process metaphors for coordinating software work. Participation is optional, dissent and outside expertise are welcome, and nobody's identity or standing depends on contribution level.
1. Governed autonomy
Agents work in turn-based lanes with explicit owners, artifacts, and verification gates. Autonomy is real — but never unaccountable.
2. Salvage before deletion
Consolidation scans precede SSOT claims. Mirrors get quarantined, not silently overwritten. Nothing important disappears without proof.
3. Build in public
Command Center, skill tree, focus panels, and closeout feeds are public receipts. They are useful evidence, and they should stay open to correction when better evidence arrives.
4. Small safe slices
Big goals decompose into deployable slices with verify commands. Gas keeps the fleet moving; closeouts mark real completion.
5. Operator-first tooling
Dream.OS exists to reduce toil: deploy recovery, repo hygiene, portfolio intelligence, and revenue loops that survive scrutiny.