Clarify Phase 5R reconciliation preservation rules
This commit is contained in:
parent
a386eed62f
commit
7461702a5c
2 changed files with 22 additions and 4 deletions
|
|
@ -153,6 +153,11 @@ For the current clean-room sequence:
|
|||
- 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
|
||||
- repo-local and shared reconciliation are additive, not reset-oriented
|
||||
- the coordinating instance must require those passes to account for all
|
||||
qualifying prior clean notes and standing reconciled notes in scope
|
||||
- the coordinating instance must not allow earlier valid effort to disappear
|
||||
silently; supersessions, exclusions, and deferrals must be explicit
|
||||
|
||||
## Closing rule
|
||||
|
||||
|
|
|
|||
|
|
@ -41,6 +41,12 @@ That means the next work is:
|
|||
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
|
||||
|
||||
Reconciliation rule:
|
||||
|
||||
- repo-local and shared reconciliation are additive passes, not reset passes
|
||||
- they must account for all qualifying prior clean notes and any existing standing reconciled notes in scope
|
||||
- they must not silently omit earlier valid effort; any rejection, supersession, or deferral must be named with rationale
|
||||
|
||||
It does not mean:
|
||||
|
||||
- reopen broad `0R` evaluation
|
||||
|
|
@ -102,8 +108,8 @@ The active four-repo restrictive queue is:
|
|||
Recommended execution order remains:
|
||||
|
||||
1. `cubing/alg.js`
|
||||
2. `cubing/twisty.js`
|
||||
3. `HactarCE/2x2x2x2-Scrambler`
|
||||
2. `HactarCE/2x2x2x2-Scrambler`
|
||||
3. `cubing/twisty.js`
|
||||
4. `kash/cubedesk`
|
||||
|
||||
Reason:
|
||||
|
|
@ -166,6 +172,10 @@ Shared optional clean `Model B` cross-lane reconciliation:
|
|||
- starts directly from the shared `0500` prompt
|
||||
- reads only the affected repos' handoffs, standing reconciled notes, and
|
||||
staged clean notes
|
||||
- must account for all qualifying prior clean notes and standing reconciled
|
||||
notes for the lanes in scope
|
||||
- must not silently drop earlier valid effort; any supersession or deferral
|
||||
must be explicit
|
||||
|
||||
Clean `Model B` bounded implementation:
|
||||
|
||||
|
|
@ -173,8 +183,8 @@ Clean `Model B` bounded implementation:
|
|||
- one repo at a time
|
||||
- one bound at a time
|
||||
- no primer by default
|
||||
- consumes the standing cross-lane reconciled note plus the repo-specific
|
||||
reconciled note
|
||||
- consumes the repo-specific reconciled note and, only if one was explicitly
|
||||
created for that lane, the shared cross-lane reconciled note
|
||||
|
||||
## Primer rule
|
||||
|
||||
|
|
@ -208,6 +218,9 @@ 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.
|
||||
|
||||
That repo-local or shared reconciliation pass must account for all qualifying
|
||||
prior clean notes in scope and must not silently omit earlier valid effort.
|
||||
|
||||
## Repo-specific lanes and current boundaries
|
||||
|
||||
### `cubing/alg.js`
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue