[Kernel][G04 G10] Consume Router execution decisions and preserve Attempt-bound route identity #52
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#60 [Kernel][G01-G13] Accept the installed controlled-task path end to end
Creatidy/creatidy-kernel
#47 [Kernel][G01 G04 G10] Prove existing harness control and gateway compatibility
Creatidy/creatidy-kernel
#51 [Kernel][G05] Propagate approved task requirements to Router without L0 fallback
Creatidy/creatidy-kernel
Reference
Creatidy/creatidy-kernel#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Priority: P2
Type: integration/acceptance.
Current Scope And Supersession
Published under the owner's 2026-10-27 bounded architecture/backlog mandate #103. PR #104 is merged at
ace7175e087cd70e207594f5631c8f4f70fabfd4; pending/prepared wording at that historical cut is not current integration status. This active content supersedes conflicting historical descriptive scope, priorities and dependencies, including dated comments, without changing their evidence or review counters. The complete pre-update body is preserved unchanged under## Historical Scope And Evidencebelow. Prepared A is registered #105 and B is registered #106. Publication does not select implementation or establish overall alignment acceptance.P2 means required integration, evidence/operability or installed reception under the integrated P0-P3 Priority Contract; lower number is earlier, not a budget or deadline. This is the single active priority. Eligibility/evidence precede priority; ranking never bypasses prerequisites, owner decisions, STOP_REVISE or exact invalid/wontfix/duplicate exclusions. Ranked-before-unranked, explicit dependency ordering, oldest registration/tie by ID and existing /loop authority remain unchanged.
Goal
Deliver full actual Router/harness execution with exact admission, sticky main route and honest identity/usage/recovery.
Why
Recommendation provenance does not enforce inference.
Scope
Resource/Harness adapters and exact supported combinations, not the work coordination core or a new gateway. Keep PR #100 negative and all previous review evidence.
Acceptance Criteria
Dependencies
Accepted #47/#51 and exact SR contracts (#174/#179/#180/#181) where consumed; closed producer state alone is insufficient. Remove #53 as a promised consumer/predecessor. No whole-product or UI prerequisite. A decision to change SR multipart semantics belongs to SR under separate authority; this CK issue records the conditional gap without mutating SR.
Constraints
ADR 0012 and ADR 0011 apply. Preserve inward dependencies (
adapters -> ports -> core) and the self-contained public core; no private repository or live-service dependency for core/offline tests. No new coding agent, tracker, catalogue, gateway or generic workflow DSL. No credential/runtime-state copying. Preserve old bytes/IDs/unknowns and #53 CLOSED / NOT IMPLEMENTED, PR #85 CLOSED / UNMERGED; its strict-expiry negative and review history are not an accepted adapter or pass. Synthetic offline tests plus the installed path and independent exact-subject review are required. Live inference/effects/releases require separate authority; this publication grants no accounts, live spending, private data access, merge, release or deployment. Preserve PR #100 as a negative receipt, not full route acceptance, and PR #101 as provenance-only, not full knowledge-content acceptance. Historical evidence and all review counters remain immutable.Links
ace7175e087cd70e207594f5631c8f4f70fabfd4).ace7175e08/docs/adr/0012-unified-work-coordination-and-drivers.mdace7175e08/docs/adr/0011-task-level-authority-and-trusted-development.mdace7175e08/docs/architecture/target.mdace7175e08/docs/architecture/migration.mdace7175e08/docs/architecture/backlog-alignment.mdace7175e08/docs/architecture/harness-feasibility.mdHistorical Scope And Evidence
Goal
Owner: Kernel consumer. Integrate the Router-owned public execution decision/admission/pin with a proved harness backend, preserving sticky main-Attempt route and distinct requested/resolved/observed identity. Router remains producer of route, source/account/quota/channel policy and gateway execution. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 brief.
Why
A recommendation validated against one Codex binding is not Router-backed inference. Users need dynamic default selection and auditable route/call identity without hidden fallback or invented physical-model guarantees.
Current Evidence
Kernel
eb4f4a2956: scarcity_router.py POST /v1/select yields model recommendation and runtime binding; compose_task_live uses one configured codex binding. Allocation is persisted before dispatch, but no gateway client/admission/resource route is consumed. Codex native configuration resolution exists; observed generated identity remains unknown. Router source at inspected 8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b distinguishes SelectionDecision from RouteDecision/admit_pinned_target; sr-pin is not approval/reservation. Gateway supports Chat Completions; Responses is deferred. No live compatibility tested.Scope
After #47 proves control/backend compatibility, consume current public producer contract, with dynamic Router choice by default and explicit user pin exception. Store route before dispatch bound to immutable Attempt; retain provider/model/resource/access mode/explicit effort/opaque variant/harness and versions distinctly. Prove main/auxiliary/review calls, tools, reconnect and uncertain effects through harness and gateway. If producer contract is missing, receive producer proof first; do not export Router internals as invented public API.
Acceptance Criteria
Reuse
Retain local allocation/effect/identity recovery and strict public transport. Evaluate Router native public selection/pin/admission/gateway with proved harness backend, not copied gateway or provider SDK stack. Verify exact revision/files/license/service-access terms/negative tests/security/dependencies/maintenance before adaptation.
Dependencies And Priority
First integration prerequisite after #47, #49 and approved requirements translation; route producer contract owned by BioMedical-IT/scarcity-router (shared alignment counterpart initially not found). Known producer cancellation issue #165 must be accounted for, not assumed solved. Kernel identity changes depend on that contract, never redesign producer identity here.
Retain the existing prerequisites: #47 control/backend proof; approved #49/#51 requirements; Router #174 executable decision/admission, #178 route identity, #179 identity/effort, #180 workspace authority, #181 protocol evidence, and #165 cancellation evidence; and an exact Kernel #52 consumer receipt. This receipt proves only Kernel-controlled route/admission and Attempt-bound identity; it does not prove strict native effect expiry. Under the accepted task-level baseline, expiry denies new Kernel-controlled dispatch and initiates bounded STOP while native local effects may continue until the exact owned task settles. Preserve the existing prohibition on source/effort/access-mode parsing or physical-attestation inference from gateway audit. #53/PR #85 remains CLOSED / NOT IMPLEMENTED; its diagnostic is neither a shipped route adapter nor an acceptance pass.
Permissions And Constraints
Live end-to-end proof needs separately authorized inference, reachable gateway/source and tool/effect scopes; plan-managed assurance or missing required identity may need owner decision. No reset/overflow/fallback authority, private runtime dependency, shared DB, routing policy or merge/deploy.
Links
Non-Goals
No Router implementation, hand-ranked models, physical identity guess, own provider stack or live task authorization from registration.
Producer Counterparts And Authority Prerequisite
Actual new producer bodies were fetched and their AC compared, superseding the initial 'not found' discovery note. These are open obligations, not implementation receipts:
Additional explicit reception condition within this issue's existing authority scope: before enabling an affected native workspace-editing lane, consume the accepted #180 authority/migration decision and prove there is no concurrent uncoordinated editor/controller, no extra workspace/network scope and no lost immutable evidence. Do not silently delete, move to scratch or relabel the producer lane. If disposition is unresolved, report that lane unaccepted; do not block unrelated documentation or manufacture a technical contract. Concrete owner conflict is D-063's current editing behavior versus the 2026-10-04 shared ownership direction, not routine infrastructure.
Order: #47 control/backend proof + approved #49/#51 requirements; producer #178/#179/#180 and #174 conformance; #181 specific protocol evidence; Kernel #52/#53 consumer receipt. No source/effort/access-mode parsing or physical attestation inference from a gateway addressed-target audit.
kilo referenced this issue from Creatidy/scarcity-router2026-10-04 23:43:29 +00:00
kilo referenced this issue2026-10-18 01:08:01 +00:00
Owner-authorized bounded Kilo 7.8.18 offline proof is preserved in PR #100 (Refs #52; keep this issue open). Exact head
c717613d0d03e1fb5ce9a9e4f3a4c3b47cc6da56, basee1aca78b0e56afffb245005e25ecb7b155a8367a.Outcome is deliberately NOT_ESTABLISHED, not product integration/adoption: real pinned Kilo appends environment context as a second user-text part; final SDK body retains opaque pin, valid full D079 context/nulls, effort and output bound, but actual Router
4162f6fa...parser refuses multipart withunsupported_parameter,messages. The parser-only string control is not a forwarded prompt rewrite. Nine native cases preserve bounded plugin/guard/pure-mode results plus unsafe publish-then-throw dispatch; mandatory enforcement is not inferred from optional hook errors.Remaining auxiliary/tool/review/compaction/fallback paths, durable Attempt send claims, ambiguous recovery/STOP/settlement and stronger isolation remain unproved after early main-path failure. TRUSTED_DEVELOPMENT only. No new product dependency, live inference, credentials, producer changes, proxy/fork/agent loop.
make checkpasses (1457 passed,85 skips,106 subtests), package-check passes, audit has no known vulnerabilities; native proof8+1 cases and actual producer checks pass as a negative regression. Independent whole-PR review is next. Fresh canonical evidence separately identifies #55 offline reference retention and #62 native migration as independently implementable; this #52 combination gate is not repository-wide inactivity.Bounded negative-proof PR #100 is integrated, not full #52 completion. Supported normal MCP merge produced
f4d86ea0a8e1b048d186fae01d49bb2283fc99d6; fetched develop contains approved headc717613d0d03e1fb5ce9a9e4f3a4c3b47cc6da56, with exact parents recorded basee1aca78b0e56afffb245005e25ecb7b155a8367aand approved head. Integrated tree is byte-identical to the reviewed/validated proof head; same checkout returned clean to exact develop.Whole-PR review counter preserved: ordinal1 COMMENT (public-reader SDK/patch access infrastructure, no findings); ordinal2 fresh APPROVE with empty findings after exact public Git objects were prepared for the unchanged reviewer. Both independently ran check/package-check; final CI3236/UI220 succeeded on exact head. The reviewer independently verified source but did not rerun the opt-in native receipt; that limit remains explicit.
Feasibility remains NOT_ESTABLISHED for this exact ordinary main-path combination: multipart native context is refused by the current producer; no prompt flattening/suppression/contract change is approved. Other inference/lifecycle/security receipts remain unproved. The issue stays OPEN, existing Codex/harness-neutral interfaces remain unchanged, and no runtime dependency/adoption/live scope is approved. Native reproducible proof and rights/limits are in tools/check_kilo52.py, tests/fixtures/kilo52/ and docs/architecture/harness-feasibility.md. Only the owner-authorized evidence slice is delivered. Unrelated eligibility is being freshly assessed independently of this issue-local gate.