docs: close lowering admission continuity gaps

Author: eldryoth

README.md

@@ -108,7 +108,7 @@ and licensing decision. See [Publication Policy](docs/PUBLICATION_POLICY.md).
 ## Documentation
 
 - [Architecture](docs/ARCHITECTURE.md)
-- [Implementation Plan — 402 exact release stops](docs/IMPLEMENTATION_PLAN.md)
+- [Implementation Plan — 403 exact release stops](docs/IMPLEMENTATION_PLAN.md)
 - [Implementation Scope Audit](docs/IMPLEMENTATION_SCOPE_AUDIT.md)
 - [Release Plan](docs/RELEASE_PLAN.md)
 - [Evidence And Roadmap Governance](docs/EVIDENCE_AND_ROADMAP_GOVERNANCE.md)

docs/AUTHORITY_REVIEWS.md

@@ -358,20 +358,21 @@ the review history remains visible.
 | 0.51.20 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-20 | Independent retained-namespace scope/evidence authority, destructive-mechanism fencing, expiry, distrust, and restore applicability review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.21 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-21 | Partition-fenced evaluation, restrictive bypass, source-status refresh, canonical clean-empty result, recovery, fairness, and current-root review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.22 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-22 | Explicit lifecycle adjacency, process-state separation, shared generation, guard-slot CAS, activation/abort/two-CAS quarantine linearization, expiry, late response, restore, and terminal-state review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.23 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-23 | Source-local activation-permit redemption, successor-restriction bridge, partition admission reconciliation, lifecycle CAS, failure closure, and non-operational-state review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.24 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-24 | Successor-restriction bridge ownership, destination acceptance, funded capacity, zero-member root, conservation, root-bound activation-preparation command/CAS, response loss, and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.23 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-23 | Closed effective-restriction admission authority, source-local activation-permit redemption, selected-restriction successor bridge, partition admission reconciliation, lifecycle CAS, failure closure, branch non-substitution, and non-operational-state review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.24 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-24 | Effective-restriction admission root, successor-restriction bridge ownership, destination acceptance, funded capacity, branch-consistent zero-member/conservation roots, root-bound activation-preparation command/CAS, response loss, and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.25 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-25 | Partial-admission rejection/unknown/revalidation handling, shared abort fence, permit/bridge disposition, zero-member root, supersession, recovery, and competing-candidate review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.26 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-26 | Permanent-unknown terminal-unavailable versus quarantine-recovery policy, catastrophe authority, prerequisites, profile claims, and no-execution-from-decision review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.27 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-27 | Conditional unknown-admission two-CAS quarantine, permanent fences, root-before-terminal, key/lease invalidation, restore/rollback floors, conservative residual capacity, and late-evidence review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.28 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-28 | Generated command/effect/workflow/plugin/admin/adapter/contribution enforcement universe, authoritative owners, registry generations, derivation agreement, invalidation and whole-domain fallback review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.29 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-29 | Maximal unknown-restriction lattice element, coverage-bound residual-root membership, mandatory evaluation/status/admission/bridge enforcement, capacity, replay, and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.30 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-30 | One-shot eligibility tombstone, bounded predecessor-linked replacement-evaluation generations, cumulative budgets, old-fence disposition, permanent exhaustion, stale receipt, response-loss, and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.51.31 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-31 | Destination-admitted one-shot lowering authority, lowering-specific evaluation root, typed source permits/command/receipts, mode fences, complete prepared bridge ownership/capacity, non-substitution, response-loss and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.32 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-32 | Current replacement receipt, closed top-or-lowered genesis authority, lowering adoption, lifecycle-bound admission-permit issuance/rebinding, eligibility non-reconsumption, response-loss and restore-floor review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.33 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-33 | Tagged initial/replacement and effective-restriction final consumption, operational transition, eligibility tombstone, deferred lowering release manifest/capacity, and dual reinstall release-work review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.34 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-34 | Reinstall delivery-barrier/evaluation-fence release or funded retention reconciliation, capacity conservation, restrictive-state preservation, recovery, and cleanup review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.35 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-35 | Operational-mode prepared-root validation, one guard-slot lowering CAS, unrelated guard preservation, activation receipt, atomic predecessor release manifest/capacity, response-loss and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
-| 0.51.36 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-36 | Predecessor-top per-enforcement-point release/funded retention, authenticated receipts/root, ownership transfer, capacity conservation, late evidence, routing, response-loss, restore and cleanup review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.32 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-32 | Current replacement receipt, closed top-or-lowered genesis authority, root-level pending lowering adoption, lifecycle-bound partition-adoption conditions, eligibility non-reconsumption, response-loss and restore-floor review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.33 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-33 | Pre-operational lowered per-partition bridge adoption, lifecycle rebinding without bridge/capacity duplication, standard admission-root folding, funded ownership transfer, branch-consistent effective-restriction admission root, response loss, abort and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.34 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-34 | Tagged initial/replacement and effective-restriction final consumption, commit-time lowering generation/expiry/revocation freshness, operational transition, eligibility tombstone, deferred lowering release manifest/capacity, and dual reinstall release-work review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.35 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-35 | Reinstall delivery-barrier/evaluation-fence release or funded retention reconciliation, capacity conservation, restrictive-state preservation, recovery, and cleanup review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.36 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-36 | Operational-mode prepared-root validation, commit-time evidence/coverage/safety/restriction/revocation/expiry/bridge/guard freshness, one guard-slot lowering CAS, unrelated guard preservation, activation receipt, atomic predecessor release manifest/capacity, response-loss and restore review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
+| 0.51.37 | `docs/implementation/ROADMAP_AUTHORITY_COMPLETIONS.md` | proposed | VIT-PAUTH-0-51-37 | Predecessor-top per-enforcement-point Released, RetainedAccepted or PendingUnknown outcomes, authenticated terminal receipts/root, zero-pending mixed aggregate completion, ownership transfer, capacity conservation, late evidence, routing, response-loss, restore and cleanup review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.60.4 | `docs/implementation/ROADMAP_COHERENCE_COMPLETIONS.md` | proposed | VIT-PAUTH-0-60-4 | Authorization-contribution certification authority review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.70.5 | `docs/implementation/ROADMAP_COHERENCE_COMPLETIONS.md` | proposed | VIT-PAUTH-0-70-5 | Workflow-contribution certification authority review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |
 | 0.100.2 | `docs/implementation/ROADMAP_COHERENCE_COMPLETIONS.md` | proposed | VIT-PAUTH-0-100-2 | Search-contribution certification authority review | before implementation resolve to exact declarations, `extends`, or reviewed `none` |

docs/EVIDENCE_AND_ROADMAP_GOVERNANCE.md

@@ -55,19 +55,19 @@ or its required evidence is unavailable, the stop remains `Specified`,
 
 ## Canonical Roadmap Cardinality
 
-The roadmap contains exactly **402 independently pentestable release stops**:
+The roadmap contains exactly **403 independently pentestable release stops**:
 
-`150 base 0.x.0 stops + 251 companion stops + 1 production stop = 402`.
+`150 base 0.x.0 stops + 252 companion stops + 1 production stop = 403`.
 
 The public `.0` skeleton still contains 151 base stops when `1.0.0` is
-included. “151 base stops” and “402 exact release stops” describe different
+included. “151 base stops” and “403 exact release stops” describe different
 views and must always be qualified. The phrases “151 phases,” “225
 milestones,” “228 exact stops,” and the superseded “229 exact stops” are not
 valid current repository descriptions.
 
 `scripts/check_implementation_plan.sh` is the current machine-checked stop
 manifest: it enumerates every companion version, requires every base version,
-and requires 402 exact-commit pentest markers. Reopened `0.1.0` must replace
+and requires 403 exact-commit pentest markers. Reopened `0.1.0` must replace
 that embedded list with, or generate it from, one canonical machine-readable
 roadmap manifest. The README, release plan, release notes, phase index,
 authority-review coverage and checker expectations must be generated or
@@ -230,18 +230,21 @@ lineage and delivery cuts, `0.51.14` owns mutation classification/emergency
 invalidation, `0.51.15–0.51.18` authorize/complete takeover, fund retained
 candidate controls, and reconcile barrier release; `0.51.19–0.51.20` own
 archival cleanup and independently verified retained namespaces; and
-`0.51.21–0.51.36` evaluate reinstall, serialize activation against abort,
+`0.51.21–0.51.37` evaluate reinstall, serialize activation against abort,
 redeem source-partition permits, fund every successor-restriction bridge,
 reconcile and supersede partial admission, decide and conditionally implement
 permanent-unknown quarantine recovery, actively enforce the maximal unknown
 restriction over a generated complete operation universe, consume replacement
 eligibility into one finite cumulative-budget evaluation lineage whose
 exhaustion is permanent, evaluate/admit lowering under separate
 non-substitutable authority, create one proof-bound fresh successor from an
-exact top-or-lowered tag, use tagged initial/replacement final activation
-without double consumption, supersede the guard, reconcile both reinstall
-release families, and make the old top survive until a destination-admitted
-fully bridged guard CAS plus authenticated funded predecessor reconciliation;
+exact top-or-lowered tag, carry lowered bridges through branch-consistent
+partition admission and funded ownership without duplication, use commit-fresh
+tagged initial/replacement final activation without double consumption,
+supersede the guard, reconcile both reinstall release families, and make the
+old top survive until a destination-admitted fully bridged fresh guard CAS plus
+zero-pending authenticated released-or-funded-retained predecessor
+reconciliation;
 none uses a wildcard tenant or cross-tenant transaction. Plugin uninstall and
 feature disablement
 never imply data retirement. `0.145.4` destructively certifies all of these

docs/IMPLEMENTATION_PLAN.md

@@ -8,16 +8,16 @@ verification, and exact-commit pentest stop. A milestone may be split before
 implementation if one review pass becomes too broad; later work may never be
 pulled into an earlier tag merely for convenience.
 
-The canonical roadmap contains 402 exact release stops: 150 base `0.x.0`
-stops, 251 companion stops, and one `1.0.0` stop. Only the limited `0.1.0`
+The canonical roadmap contains 403 exact release stops: 150 base `0.x.0`
+stops, 252 companion stops, and one `1.0.0` stop. Only the limited `0.1.0`
 repository/N0 scaffold is currently executable, and its release status remains
 reopened. Every other capability is `Specified` until its versioned executable
 owner and evidence gates pass. The authoritative claim vocabulary, cardinality
 law, production-profile boundary, and protocol-specification extraction rules
 are in [Evidence And Roadmap Governance](EVIDENCE_AND_ROADMAP_GOVERNANCE.md).
 The [Implementation Scope Audit](IMPLEMENTATION_SCOPE_AUDIT.md) applies the
 small-loop rule to every stop, assigns 65 decomposition companions to the 18
-families that exceeded it, and records 108 later focused capability,
+families that exceeded it, and records 109 later focused capability,
 requirement-ownership, decomposition, integration, discovery, and coherence
 companions.
 
@@ -103,18 +103,21 @@ proves partition currency and canonical empty state, `0.51.14` owns urgent
 restrictive invalidation, `0.51.15–0.51.18` authorize/complete takeover,
 atomically fund retained candidate controls, and release its barriers,
 `0.51.19–0.51.20` archive cleanup and verify retained namespaces, and
-`0.51.21–0.51.36` evaluate reinstall, linearize activation against abort,
+`0.51.21–0.51.37` evaluate reinstall, linearize activation against abort,
 obtain source-partition admission, fund durable bridge ownership, terminate or
 supersede partial admission, decide and conditionally implement conservative
 permanent-unknown quarantine recovery, actively enforce the maximal unknown
 restriction over a generated complete operation universe, run one finite
 cumulative-budget replacement-evaluation lineage with permanently terminal
 exhaustion, evaluate/admit lowering under separate non-substitutable authority,
 create exactly one fresh proof-bound successor from a closed top-or-lowered
-tag, use tagged final activation without re-consuming replacement eligibility,
-consume the completely admitted successor, release both candidate-control
-families, lower an operational guard only through a fully prepared CAS, and
-release the old top only through authenticated funded conservation.
+tag, carry either branch through one tagged admission/ownership pipeline,
+adopt every prepared lowered bridge without duplication, use commit-fresh
+tagged final activation without re-consuming replacement eligibility, consume
+the completely admitted successor, release both candidate-control families,
+lower an operational guard only through a commit-fresh prepared CAS, and
+release the old top only through zero-pending authenticated funded
+reconciliation.
 `0.145.4`
 destructively certifies
 selected retirement/reinstall profiles rather than first implementing teardown.