G06: Consume admitted Model Intelligence snapshots with provenance and a safe catalog migration #176
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
Reference
Creatidy/scarcity-router#176
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?
Current Owner-Authorized Delivery (2026-10-26)
Adrian's direct directive at 2026-10-26T00:01:13Z resumes #176 and authorizes bounded initially non-disruptive MI consumer implementation, validation, independent native Kilo review and /loop integration. The order is accepted MI publication -> Router #176 consumer -> MI #19 installed integration acceptance. Kernel #55 is a separate downstream utilized-reference consumer. Do not invert these dependencies. Router #181/#185 are merged. The former interpretation that activation-policy approval blocks even inactive implementation is superseded.
Implementation acceptance for this delivery: reuse the exact accepted producer contract at MI
d65891668b7e79f7b666c021f02a1b4bf8c4ca9c, including/2; independently validate expected cut/reference/digest/version/scope/source coverage/history; preserve exact applicability; capture immutable cut and evaluation context BEFORE the shared selector; actually use supported public evidence in its explanation path; emit the accepted immutablemi_utilizationreference with retained result/context/cut/manifest artifacts. An explicit library-only explanation path is authorized; it must preserve bootstrap ratings/hard limits, local policy, private capacity/entitlement/billing and execution identity. No default/live activation, automatic calibration, replacement catalog/producer/evidence DB or MI/Kernel mutation. Require deterministic producer-consumer negative/refresh/bootstrap/binding conformance tests and all repository gates, fresh complete-PR correctness/security/UX review and exact-currentness integration. The minimum active-admission proposal is separate and must not be silently enabled. Router tests do not pass MI #19 installed acceptance or Kernel #55.Goal
Product owner: Scarcity Router (consumer); Model Intelligence owns publication. G06/G13. Source: Creatidy architecture v1.0 (2026-10-04), sections 1-5, 7-13, 14-18 via #173. Prove the producer-consumer knowledge contract, then support admitted versioned MI snapshots without a second public-facts source of truth.
Why and Evidence
Historical registration baseline: Router develop
8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1bloaded curated model-catalog/model-policy and reviewed tracks without an MI consumer. MI #9 was proof-only; this is now superseded for producer availability by accepted MI #13 publication, #15 production producer and the verified native/2payload at the exact revision above. Use actual integrated contracts, never predecessor experiments or unmerged feature output as authority.Scope and Non-Goals
Consume the actual versioned MI producer artifact, preserving publication ownership, retained revisions, artifact compatibility, effective validity/freshness and conflict/withdrawal semantics. Preserve working catalog/tracks as bootstrap until separately accepted replacement. Router retains local policy/private state and calibration decisions; MI owns public facts/provenance/versions. No Router crawler, benchmark service, independent public facts DB, MI private credentials/quota, mandatory daemon/broker/shared DB, universal score or automatic learning.
Acceptance Criteria
Dependencies and Priority
Next foundational lane. MI #13/#15 publication, Router #181/#185 are satisfied; no wait for MI #19 or Kernel #55. Original MI #9 proof reference: Creatidy/model-intelligence#9. Actual installed consumer integration is downstream Creatidy/model-intelligence#19; utilized-reference adoption is Creatidy/creatidy-kernel#55. Preserve G10/G13 compatibility and G04 provenance. Refs #173; #117/#124 are source inventory, not installed MI coverage.
Constraints and Remaining Acceptance
Evaluate ADOPT first; reuse producer validation/projection/utilization rather than duplicating them. Any dependency/copied data has exact revision/license/attribution and semantic/security/negative checks. Forgejo remains canonical; no unauthorized GitHub-reference migration. No removal of human-reviewed ratings without provenance/date/confidence/rationale/diff. Active new-use admission/calibration policy approval and separately installed MI #19/Kernel #55 receipts remain distinct future gates, not implementation prerequisites. Live calls require separate authority; no inference is needed for deterministic component proof.
Closeout counterparts now exist: MI publication producer Creatidy/model-intelligence#13, production acquisition/publication #15, identity/calibration #14, distribution/migrations #18, installed update/outage receipt #19. Kernel downstream provenance consumer: Creatidy/creatidy-kernel#55. All OPEN; #9 remains bounded proof only. MI #13 explicitly requires a frozen evidence cut plus evaluation semantics: knowledge(evidence, at) alone does not reconstruct historical acquisition and absent freshness does not prove freshness. Publication proof/admission and #185 compatibility -> Router consumer/bootstrap migration -> Kernel retains actual utilized references -> composed installed outage/withdrawal acceptance. No mandatory per-inference MI lookup or private telemetry export.
Fresh new-/loop dependency tracing confirms actual MI producer exists at938f4160493359f9795c3bda081b065afac96b16: accepted13/14 contracts, integrated15 acquisition/publication,16 operator,18 distribution. Public source and1/2payload migration inspected; no missing-MI15 contract claim. Formal Router dependency is185, whose own existing-contract compatibility work was independently assessed rather than treating its open status as a blocker.
Remaining Router-owned conditions:185 compatibility before activation; actual admitted decoder/activation/provenance/bootstrap migration; explicit approved private admission/calibration/freshness policy from this issue's constraints. Research/design can proceed, but green MI/source commits alone do not approve private calibration or prove Router consumption. MI19 stillrequiresinstalledRouter176consumer and is DOWNSTREAMacceptance, not176implementation gate.
Normalpriority selected174 first and implementedPR204; invocationnow STOP_REVISE for that started delivery's mandatory security findings/insufficient fresh-gate review capacity, not queue inactivity. Currentdevelopedd31326d4abe5cc282adb419cb54c78d4677ec4. No176consumer/activation/installedreceipt/closure claimed, no cross-repository mutation or newplanningcontroller.
kilo referenced this issue2026-10-12 22:57:07 +00:00
2026-10-24 /loop dependency-evidence refresh after requested PR reconciliation: actual MI develop is
d65891668b7e79f7b666c021f02a1b4bf8c4ca9c(fresh canonical Git read). Inspected exact PUBLICATION_CONTRACT.md, pyproject and producer/publication/conformance ownership declarations from a transient read-only public-object clone; no MI mutation, import/execution or private data. MI13/PR26 and MI15 are integrated; the current package exposes framing plus /1 and explicit /2 native-limit evidence, immutable publication and utilization contracts. Thus no missing-MI-publication/MI15 implementation claim is valid. Working version0.1.0 is not a permanent ABI; configured freshness/calibration/private new-use admission are explicitly Router-owned, not granted by MI. /2 has no installed Router adoption at this source; producer fixtures remain honest about that.Remaining specific stages: #185's Router-owned compatibility/integration acceptance remains pending exact current ordinary/security authority; private admission/calibration/freshness mapping needs the explicit owner approval required by this issue before activation or bootstrap replacement. Already pinned use versus missing refresh/critical withdrawal stays distinct; no blanket MI outage cancellation or automatic mapping/rating change is approved. Research can proceed without live access; this read-only contract check is not consumer implementation/activation or installed acceptance. MI19/Kernel55 downstream receipts do not gate upstream research. Preserved current catalog/bootstrap and no cross-product dependency fabrication; other independent queue work remains eligible.
Fresh owner /loop invocation 2026-10-25T23:28:30Z, dependency-evidence refresh. Designated checkout is clean develop/HEAD/origin-develop
287fd5781f6713a4d5fbb273a9c24305fc58e50a; canonical Git fetch and MCP reads succeeded. Exhaustive open-issue refresh: pages1/2 contain6 each, page3 empty (12 actual issues). Exact case-insensitive wontfix exclusions only:132/139/140/141/165/166. No new implementation, review ordinal, merge or closure in this invocation.Changed condition: #185 is CLOSED and PR209 actually MERGED as287fd578. Actual Git ancestry verifies reviewed implementation11db0cb; current integrated docs/machine-interfaces.md:732-774 preserve the accepted compatibility matrix and distinguish remaining adoption. Receipt18923 records whole-PR review17 APPROVE/findings[] at HEAD11db0cb/base40f2d545, with original history retained. The prior pause/unresolved transition finding is historical, not a current #176 prerequisite. This invocation neither remerges nor claims credit for that earlier delivery.
#176: freshly rechecked actual MI develop
d65891668b7e79f7b666c021f02a1b4bf8c4ca9cand PUBLICATION_CONTRACT.md: working framing/digest, /1-/2 and bounded production publication exist; producer explicitly does not grant private admission/calibration/freshness policy. Thus NO missing-publication or unfinished185 claim. Remaining implementation/activation gate is this issue's explicit owner approval for admission/calibration policy (scope/freshness/conflict/withdrawal/mapping/bootstrap authority); current accepted Router matrix explicitly leaves raw MI payloads non-admitted. Owner: Router owner, with MI producer facts. Required action is approve an exact policy before activation; existing read-only contract research is not undone or a reason to repeat completed work. MI19/Kernel55 installed receipts are downstream acceptance, NOT upstream implementation prerequisites.Other nonexcluded queue conditions, independently assessed rather than blocked by176:
-177:174/184 prerequisites are delivered, not inferred missing. Kernel develop freshly confirmed
e1aca78b0e56afffb245005e25ecb7b155a8367a; actual adapters/task_execution.py:1245-1358 remains thin schema1 export with Attempt/allocation/operation/candidate facts, not authorized role-route/internal-call/usage/full-cost lineage. Current docs/architecture/successor.md G07/G12 explicitly distinguishes three incomplete export paths and retains52/56/58 producer work. Owner Kernel; full consumer implementation requires actual agreed producer fields/negative/privacy fixtures. No task/export/private data execution or cross-repository mutation. Actual installed whole-path coverage remains UNVERIFIED; source is not a live receipt.-183:179 delivered. Explicit140 state-correctness predecessor is excluded, not reopened. Current control_api.py:1519-1530 counts only static _config.resources and1563-1582 iterates only them: missing derived-resource guarantees are actual source evidence, not open-status inference. Owner Router; prerequisite correctness/disposition must be resolved before exposing those guarantees. Console/browser receipt stays downstream acceptance.
-186:185 now satisfied. Formal139/141 predecessors and explicit release-readiness ordering remain unmet; both predecessors are excluded, not available tasks to resurrect. Owner Router/release owner; resolve those prerequisite scopes/disposition or provide accepted equivalent TLS/composed evidence. Publication/signing/real platform actions remain separately authorized; paid execution is not invented as an offline artifact gate. Installed Windows/signing/composed proofs remain UNVERIFIED, not asserted impossible.
-199: actual Kernel scarcity_router.py still explicitly implements /v1/select recommendation only, not an executable Attempt-bound consumer; current successor map and52/60 distinguish missing replacement/installed reception. Owner Kernel supplies equivalent consumer/workspace/replacement receipts; Router owner separately accepts exact migration and authorizes incompatible retirement. This issue explicitly gates implementation on those receipts; no legacy removal or synthetic replacement claim.
-214: integrated offline HEAD
e5c8d8fancestry verified; actual pure unregistered providers/claude_statusline.py and U015 remain containment, not an active collector. Completed offline work is not repeated. Remaining allowed-source original-observation/permission/control evidence gates acquisition/activation; live account entitlement/billing/stream/cancellation acceptance is DEFERRED and requires separate owner authority. No live probe, credential handling or supported-route claim.Result: no verified eligible new full delivery in this repository at this fresh queue observation. Research availability is not called impossible; completed source research and offline deliveries stay completed. Existing owner prerequisites, verified missing producer/correctness requirements and UNVERIFIED installed/live checks are distinct. No new owner decision is manufactured, no review budget reset, no speculative issue or second controller, no Daybreak/main/release/deployment.
Owner-resumed delivery 2026-10-26T00:01:13Z supersedes comment18928's implementation-ineligible assessment. Direct owner instruction selects176 and authorizes bounded inactive/explicit-input implementation, ordinary independent review and accepted-scope /loop integration; MI19 and Kernel55 are downstream consumers/acceptance, never implementation prerequisites. #185/#181 are integrated. Base287fd5781f6713a4d5fbb273a9c24305fc58e50a, branch issue-176-mi-consumer; no previous176 implementation PR/review dispatch in canonical history, default maximum10 retained.
Scope/threat/complexity: one optional exact-pinned public MI package dependency (Apache-2.0, no runtime dependencies) reusing publication/contract/projection/utilization, bounded untrusted local publication inputs, immutable capture before actual shared selector evaluation, explanation-only supported public evidence use and exact utilization binding. No copied producer/calibration/evidence DB, live inference, service/network/auth expansion, default activation or replacement bootstrap. Exact channel/configuration/effort association is caller-explicit; unsupported mappings remain non-mapping. Full source/negative/package/type/UX/security review applies. 120-minute engineering/recovery budget, at most3 materially distinct recovery attempts per obstacle; default10 whole-PR reviews. No downstream receipt, existing activation-policy approval, or account is required to implement/test this non-disruptive scope. Active new-use policy, critical-report actions, calibration/replacement and installed/live acceptance remain separate gates. Minimum policy proposal will be recorded in existing documentation, not automatically enabled.
Owner-authorized #176 implementation ACCEPTED and integrated through PR221 BioMedical-IT/scarcity-router#221 at merge4162f6fa9f774beaf6e92d86b7ebc92f306da4bd (2026-10-26T01:06:36Z). Canonical MCP merged=true and fetched develop agree. Merge parents are exact approved base287fd5781f6713a4d5fbb273a9c24305fc58e50a / HEADfdc85f17049d7b25d1f8a85f7ea98829a6595916; ancestry passes and integrated tree equals approved treeb0798f2a98499248072f9680ff4d84838b9e1fc6. Commits59e4434/f72cb32/fdc85f1 preserved, branch retained.
Delivered acceptance1-6 for the owner-staged inactive/explicit-input scope: exact canonical MI dependency d65891668b7e79f7b666c021f02a1b4bf8c4ca9c; bounded independently expected publication reference/digest/schema/scope/source/history validation and atomic rejection; exact caller-reviewed applicability; explicit unknown/future/stale/conflict/withdrawal/unsupported dispositions and conservative retraction restoration; actual pre-selector public-fact explanation use, with cut captured before collectors and complete local context frozen before selector; exact result/context/cut/utilization retained and accepted mi_utilization reference emitted/verified; bootstrap ratings/hard limits/private capacity/policy/entitlement/physical execution authority unchanged. No exporter/network/current-pointer polling, cancellation hook, duplicate producer/catalog/calibration DB or automatic activation.
Validation:16 actual producer-to-shared-selector conformance tests pass (also rechecked after merge against exact tree equality); final full make check3048 tests OK/18 skips and type0 errors/warnings; explicit managed basedpyright clean; full wheel/sdist/isolated CLI/defaults/MCP/loopback REST package-check pass; canonical offline uv sync and diff/staged whitespace pass. Whole-PR reviews1/2 REQUEST_CHANGES remedied; fresh visible native review3 APPROVE/findings[]/limitations[] at exact integrated parents, source/tool/context provenance recorded in PR comment18951. No approval inferred from tests, UI or model self-report.
Closing only the authorized implementation delivery, NOT active-routing admission or MI19/Kernel55 installed acceptance. MI19 must now install the actual producer/Router components and verify exact utilized refs plus retained cut/context/result/manifest artifacts across real installed refresh/replay. Kernel55 remains downstream reference adoption. One concrete active-admission proposal is D082: explicit opt-in exact trusted refs/version/scope/source/full applicability; fresh-at-evaluation positive use only; no conflict winner; critical-revocation withholding with admissible retraction restoration; no quality/calibration/bootstrap replacement, entitlement/billing inference or retroactive rewrite. This proposal is NOT accepted or activated. MI19 was not waited on; no MI/Kernel/GitHub mutation, main/release/deploy or Daybreak.
Post-completion /loop SELECT/dependency refresh (same primary invocation): canonical open actual issue pages1-6 at limit2 contain11 records; page7 empty. Fresh bodies/comments/native dependency lists inspected for every nonexcluded issue. Exact wontfix exclusions only132/139/140/141/165/166; those issues were not selected or resurrected. #176 actual state CLOSED, implementation is not activation-gated or waiting for MI19. Same checkout returned by ordinary fast-forward to clean develop/origin4162f6fa9f774beaf6e92d86b7ebc92f306da4bd, issue branch/history retained.
Remaining repository-scoped conditions, backward-traced by stage/owner rather than using closed/open state alone:
-177:174/184 integrated and not missing. Fresh Kernel head still e1aca78b0e56afffb245005e25ecb7b155a8367a, same actual inspected Task-export/reference/outcomes source and successor G07/G12 map. Required full route/internal-call/usage/accepted-result lineage is absent from the actual production exporter, not merely Kernel58 OPEN. Kernel52/56/58 own producer implementation/contract/negative/privacy fixtures before the FULL Router consumer. Bounded source research was completed; no invented zero-cost fields/sidecar schema. Installed full-path receipt remains UNVERIFIED downstream acceptance.
-183:179 delivered; native dependency140 and body explicitly put its correctness guarantees first. Actual static-only state/resources regions in control_api.py1519-1530/1563-1582 are unchanged by221, so derived-state guarantees remain absent. Router owns required correction/disposition;140 remains excluded, not an eligible predecessor. Console browser/install receipt stays later acceptance, not the cause of this implementation gate.
-186:185 delivered; native139/141 dependencies and explicit required release-readiness ordering remain. Router/release owner owns prerequisite scope/disposition and separately authorized registry/signing/platform evidence. No paid-execution dependency invented for offline artifact study; source research is not declared impossible. Windows/signing/installed composed receipts remain UNVERIFIED acceptance/activation, not proof of missing build implementation. No publication, CI credential or private platform access authorized.
-199: exact Kernel head unchanged; actual scarcity_router.py remains recommendation-only and successor map52/60 preserves replacement/installed reception gaps. Kernel owns equivalent Attempt-bound replacement/consumer/composed implementation and evidence; Router owner separately accepts exact migration/retirement. Body explicitly gates substantive legacy transition on those receipts. Neither221 provenance nor a synthetic pass supplies retirement authority.
-214: offline parser/evidence/tests already integrated and accepted; U015 original-observation/source permission/control gaps remain. Owner/provider terms evidence required before acquisition/activation; separate account/live tests remain DEFERRED acceptance. No completed offline work is repeated and no prompt/token/paid fallback is invented as recovery.
Fresh MI head remains d65891668b7e79f7b666c021f02a1b4bf8c4ca9c and its actual installed/pinned contract is consumed by completed176; MI19/Kernel55 are downstream, not implementation blockers. No other verified eligible full delivery under the remaining explicit prerequisites at this observation: QUEUE_EMPTY scoped only to this repository, with exact exclusions, verified unmet source/ordering gates and UNVERIFIED installed/live checks distinguished. No whole-program inactivity/product GO assertion. D082 policy proposal remains separately unaccepted without delaying the delivered component or creating a new cleanup project.