diff --git a/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md b/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md
index fdc2a97..b47dc25 100644
--- a/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md
+++ b/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md
@@ -145,6 +145,14 @@ For the current clean-room sequence:
 - it does not mean those repos are already implemented
 - it does not mean queue presence is proof of merit beyond the already-closed retained-set and packet decisions
 - the prompt pack is routing authority, not product-surface proof
+- the default operator flow is repo-local:
+  - `Model A`
+  - clean `Model B` primer
+  - clean `Model B` contribution
+  - repo-local consolidation
+  - bounded implementation one bound at a time
+- shared cross-lane reconciliation is an exception checkpoint, not the default
+  immediate next step after every contribution pass
 
 ## Closing rule
 
diff --git a/docs/HYPERTWIST_PHASE_5R_CLEAN_ROOM_PROMPT_AND_HANDOFF_PACKET_2026-05-14.md b/docs/HYPERTWIST_PHASE_5R_CLEAN_ROOM_PROMPT_AND_HANDOFF_PACKET_2026-05-14.md
index fa8e3dd..aa070bb 100644
--- a/docs/HYPERTWIST_PHASE_5R_CLEAN_ROOM_PROMPT_AND_HANDOFF_PACKET_2026-05-14.md
+++ b/docs/HYPERTWIST_PHASE_5R_CLEAN_ROOM_PROMPT_AND_HANDOFF_PACKET_2026-05-14.md
@@ -12,7 +12,8 @@ It records:
 - the current restrictive-lane execution topology after `Phase 4R-F`
 - the exact per-repo prompt-pack files
 - the current primer rule
-- the cross-lane clean consolidation route
+- the repo-local consolidation route
+- the optional shared cross-lane checkpoint route
 - the bounded clean implementation route
 - the restart-safe handoff prompt for a new instance
 
@@ -36,8 +37,9 @@ That means the next work is:
 
 1. source-exposed `Model A` refresh and strengthening per restrictive repo
 2. clean `Model B` contributor passes per restrictive repo
-3. one shared clean cross-lane consolidation pass
+3. repo-local clean `Model B` consolidation per restrictive repo
 4. bounded clean implementation one repo and one bound at a time
+5. shared cross-lane reconciliation only when a repo-local consolidated note still flags real overlap
 
 It does not mean:
 
@@ -150,11 +152,20 @@ Clean `Model B` contributor:
 
 Clean `Model B` consolidation:
 
-- one fresh clean cross-lane thread
+- one fresh clean repo-local thread per repo
+- no primer by default
+- starts directly from the repo-local consolidation prompt inside the repo's
+  sequence file
+- reads the repo's scrubbed `Model A` handoff plus that repo's clean `Model B`
+  staged notes
+
+Shared optional clean `Model B` cross-lane reconciliation:
+
+- one fresh clean thread only when needed
 - no primer by default
 - starts directly from the shared `0500` prompt
-- reads the four scrubbed `Model A` handoffs plus the clean `Model B` staged
-  notes
+- reads only the affected repos' handoffs, standing reconciled notes, and
+  staged clean notes
 
 Clean `Model B` bounded implementation:
 
@@ -182,6 +193,21 @@ The primer is a context-loading and workflow-selection prompt.
 It is not the controlling output contract for contribution, consolidation, or
 bounded implementation.
 
+## Current Phase 5R sequencing rule
+
+Default operator flow:
+
+1. run one restrictive repo at a time
+2. complete `Model A`
+3. complete clean `Model B` primer and contribution
+4. complete repo-local consolidation for that repo
+5. implement that repo one bound at a time
+
+Shared cross-lane reconciliation is not the default next move.
+
+Use it only when the repo-local consolidated note still says a real owner-boundary
+or shared-contract overlap needs explicit coordination before implementation.
+
 ## Repo-specific lanes and current boundaries
 
 ### `cubing/alg.js`