Repository navigation
Plan four product-specific lanes and independent Workspace startup - #209
Merged
Merged
Conversation
pcvantol
marked this pull request as ready for review
October 1, 2026 14:17
This was referenced Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Owner outcome
Implements the 2026-10-01 owner decision to move from two pooled Work lanes to four product-specific lanes while retaining the ongoing installer and native credential qualification. Owning planning assignment: #207. Workspace first-slice register: #208.
Scope
New human/machine-readable federated allocation, four-lane ready-frontier/resource policy, new lane routers, AGENTS active-plan routing, and 12 offline planning guards. All 34 historical families, 158 exclusive rollup IDs, seven shared IDs and 31 source references are inherited from the existing canonical inventory/allocation, not copied into a second backlog. Later owning nodes inherit their repository lane; unknown owners/edges block selection. Existing product edges, source/evidence status authority, historical receipts and active assignments remain intact.
This is not a runtime scheduler or a claim of four-way EP execution. It does not claim a full current audit of every owning source graph, a mathematically optimal schedule, a fourfold speedup or a new hour/PR forecast. Source work is parallel; shared privileged host effects, signer identity and reboot windows remain exclusive and separately authorized.
Validation and limits
JSON construction and local test-file syntax were prepared; full repository validation has not been executed in the current container because the repository could not be downloaded there (network resolution unavailable). The new guards are included in existing unittest discovery and must pass on this exact PR head along with all required protected checks. No independent review, merge or runtime PASS is claimed by opening this draft.
No product runtime/version/release, Mission, CENTRAL, credential, account, service, host or peer source mutation. NO_BUMP. Workspace entry/backlog/DAG routing is a separate owning documentary PR before that Work executor starts implementation. Forge Platform and EP entrypoint adoption stays with their existing source owners; no second writer was introduced there.