Domestique

domestique

Project configuration for a multi-model orchestration workflow in Claude
Code, Codex and GitHub Copilot: an orchestrator designs and adjudicates,
an implementer executes, and a fresh reviewer independently verifies.
The plan of record lives in Beads.
Delegating implementation and verification keeps the orchestrator's context
lean; “done, tests pass” is checked, not trusted.

v0.4.3: retain removed providers without reactivating them

An explicit unrelated-provider install, such as dom --platform copilot, no
longer reactivates completely removed Claude/Codex projections merely because
owned metadata remains. v0.4.3 preserves that metadata, pristine bases, host
policy bytes and inactive guest Beads markers. This requires actual safe
absence: surviving partial, unowned, guard-tampered or unsafe files still undergo
validation. Explicitly selecting a damaged pair still refuses; --force does
not bypass these checks. Legacy Codex canonical shared ownership still refuses
reassignment.
After publication to main, optionally preview with
dom --platform copilot --dry-run, then run dom --platform copilot.
The covered case needs neither --force nor manual metadata repair.
See evidence and limits.

The v0.4.2 fix remains: recognition of five verified historical policy-base identities omitted by
v0.4.1, including the public 99e6274 Claude base. Unknown or modified bases,
current-guard tampering and selected-policy conflicts still refuse; --force
does not bypass these checks. Very early ff41544 installs still fail the
independent complete-inventory check: this is not support for every historical install.

The v0.4.1 fix remains: custom workflows in unselected or inactive retained
policies are preserved instead of attempting an unrelated full workflow upgrade. Known-owned…