Creatidy/scarcity-router

Fork 0

Implement approved D-082 opt-in MI selection and admission with real-source applicability proof #222

New issue

Closed

opened 2026-10-26 22:58:57 +00:00 by kilo · 2 comments

kilo commented

2026-10-26 22:58:57 +00:00

Member

Goal

Implement the conservative D-082 active-admission policy explicitly APPROVED by Adrian's direct owner directive2026-10-26T22:57:22Z. Deliver useful explicitly enabled MI participation in actual Router selection/admission, preserving default behavior and completed #176/MI19. Owner authorizes scoped follow-up registration, implementation, validation, native independent Kilo review and integration into develop; NOT production activation/release/deploy.

Why

#176/PR221 delivered validated explanation-only explicit-input consumption at Router4162f6fa9f774beaf6e92d86b7ebc92f306da4bd. MI19 is now CLOSED with independently accepted installed interoperability at MI8f572c332db8290b5dad9e03f5b0f960271a8349, not active admission. D082's formerly proposed policy is now owner-approved for implementation. Current selected Z.ai/models.dev native publications must be inspected honestly: missing model/channel/configuration/effort or explicit freshness cannot be guessed into authorization.

Scope

Reuse existing optional MI consumer/producer validation/projection/utilization. Add a default-off Router-owned policy at the existing selection/routing/pinned-admission boundaries. Enforce independently trusted exact reference/schema/scope/source/history, reviewed exact applicability, explicit freshness, no silent conflict winner, conservative withdrawal/critical revocation and admissible restoration. Supported native allowances can only conservatively intersect existing authority; no expanded quality/hard constraints/private entitlement/quota/physical-identity claims. Keep bootstrap/default path compatible and prior decisions immutable. Retain exact utilized cut/evaluation/result evidence. Inspect current actual Z.ai/models.dev source/publications read-only, establish real positive use where genuinely supported or prove concrete missing fields/owner/earliest producer-or-curator remedy without circular dependency. No duplicate catalog/rater/producer/DB/service or speculative PoC.

Acceptance Criteria

Record direct owner approval in D082 and this canonical issue; existing completed issues remain closed.
Explicit opt-in policy changes actual selector qualification/limits and executable/pinned-admission outcomes with supported trusted evidence; default routes remain unchanged. Existing auth/compatibility/limits/identity gates cannot be bypassed.
Unknown/stale/future/conflicting/withdrawn/unsupported evidence cannot positively authorize opted-in facts; critical reports conservatively withhold, and invalid retractions do not restore. Failed loads retain bootstrap/local policy and old decisions but cannot grant new admission.
Freeze original cut and policy/evaluation context before decision; utilization binds actual result and retained artifacts, including replay and refresh races.
Deterministic behavior-focused positive/negative/bootstrap/immutability tests use actual MI codecs and existing selector/route/admission seams. Inspect actual current Z.ai/models.dev publications separately from controlled fixtures, retain exact references/timestamps/provenance/limitations and do not claim synthetic real-source acceptance. If no compatible positive fact exists, document exact missing applicability/freshness and independently executable remediation rather than block this implementation or fabricate activation.
Required uv sync/make check/managed basedpyright/whitespace and packaging when affected; fresh complete-PR independent correctness/security/UX review and exact-currentness Forgejo merge into develop; verify integrated acceptance before closure.

Constraints

Security-sensitive untrusted public evidence boundary; rigorous ordinary independent review under D081, default maximum10 whole-PR reviews,120-minute technical recovery/3 materially different attempts per obstacle. One branch/PR/designated checkout and mutator. No inference/live provider-account tests, production activation, release/deployment/main, credential handling/storage, hidden model runner, MI/Kernel mutation, GitHub canonical reference migration, automatic calibration/rating change or bootstrap replacement. Exact public source data rights/provenance and code licenses remain separate. No arbitrary network endpoint or new service.

Links

D082 docs/decisions.md and docs/machine-interfaces.md explicit MI consumer
Completed Router #176 / PR221
Creatidy/model-intelligence#19
Creatidy/model-intelligence@8f572c332d/INSTALLED_ACCEPTANCE.md
MI canonical contract PUBLICATION_CONTRACT.md and modules contract/publication/projection/utilization/zai

## Goal Implement the conservative D-082 active-admission policy explicitly APPROVED by Adrian's direct owner directive2026-10-26T22:57:22Z. Deliver useful explicitly enabled MI participation in actual Router selection/admission, preserving default behavior and completed #176/MI19. Owner authorizes scoped follow-up registration, implementation, validation, native independent Kilo review and integration into develop; NOT production activation/release/deploy. ## Why #176/PR221 delivered validated explanation-only explicit-input consumption at Router4162f6fa9f774beaf6e92d86b7ebc92f306da4bd. MI19 is now CLOSED with independently accepted installed interoperability at MI8f572c332db8290b5dad9e03f5b0f960271a8349, not active admission. D082's formerly proposed policy is now owner-approved for implementation. Current selected Z.ai/models.dev native publications must be inspected honestly: missing model/channel/configuration/effort or explicit freshness cannot be guessed into authorization. ## Scope Reuse existing optional MI consumer/producer validation/projection/utilization. Add a default-off Router-owned policy at the existing selection/routing/pinned-admission boundaries. Enforce independently trusted exact reference/schema/scope/source/history, reviewed exact applicability, explicit freshness, no silent conflict winner, conservative withdrawal/critical revocation and admissible restoration. Supported native allowances can only conservatively intersect existing authority; no expanded quality/hard constraints/private entitlement/quota/physical-identity claims. Keep bootstrap/default path compatible and prior decisions immutable. Retain exact utilized cut/evaluation/result evidence. Inspect current actual Z.ai/models.dev source/publications read-only, establish real positive use where genuinely supported or prove concrete missing fields/owner/earliest producer-or-curator remedy without circular dependency. No duplicate catalog/rater/producer/DB/service or speculative PoC. ## Acceptance Criteria 1. Record direct owner approval in D082 and this canonical issue; existing completed issues remain closed. 2. Explicit opt-in policy changes actual selector qualification/limits and executable/pinned-admission outcomes with supported trusted evidence; default routes remain unchanged. Existing auth/compatibility/limits/identity gates cannot be bypassed. 3. Unknown/stale/future/conflicting/withdrawn/unsupported evidence cannot positively authorize opted-in facts; critical reports conservatively withhold, and invalid retractions do not restore. Failed loads retain bootstrap/local policy and old decisions but cannot grant new admission. 4. Freeze original cut and policy/evaluation context before decision; utilization binds actual result and retained artifacts, including replay and refresh races. 5. Deterministic behavior-focused positive/negative/bootstrap/immutability tests use actual MI codecs and existing selector/route/admission seams. Inspect actual current Z.ai/models.dev publications separately from controlled fixtures, retain exact references/timestamps/provenance/limitations and do not claim synthetic real-source acceptance. If no compatible positive fact exists, document exact missing applicability/freshness and independently executable remediation rather than block this implementation or fabricate activation. 6. Required uv sync/make check/managed basedpyright/whitespace and packaging when affected; fresh complete-PR independent correctness/security/UX review and exact-currentness Forgejo merge into develop; verify integrated acceptance before closure. ## Constraints Security-sensitive untrusted public evidence boundary; rigorous ordinary independent review under D081, default maximum10 whole-PR reviews,120-minute technical recovery/3 materially different attempts per obstacle. One branch/PR/designated checkout and mutator. No inference/live provider-account tests, production activation, release/deployment/main, credential handling/storage, hidden model runner, MI/Kernel mutation, GitHub canonical reference migration, automatic calibration/rating change or bootstrap replacement. Exact public source data rights/provenance and code licenses remain separate. No arbitrary network endpoint or new service. ## Links - D082 docs/decisions.md and docs/machine-interfaces.md explicit MI consumer - Completed Router #176 / PR221 - https://forgejo.creatidy.com/Creatidy/model-intelligence/issues/19 - https://forgejo.creatidy.com/Creatidy/model-intelligence/src/commit/8f572c332db8290b5dad9e03f5b0f960271a8349/INSTALLED_ACCEPTANCE.md - MI canonical contract PUBLICATION_CONTRACT.md and modules contract/publication/projection/utilization/zai

kilo commented

2026-10-26 23:14:03 +00:00

Author

Member

ACTUAL public-source investigation 2026-10-26T22:59:29.062118Z used existing MI acquisition.fetch with its original source allowlist/byte bounds and sanitized credential-free environment, no redirects, model calls, files or publication. The actual eight-source generation was incomplete: pricing https://docs.z.ai/guides/overview/pricing.md exceeded declared2620-byte bound. A separate diagnostic-only larger bounded request (not producer normalization/input/policy) then returned HTTP500/source-retrieval-failed; no blind retry or widened producer config. Seven successful actual reads:

catalog models/zhipuai/glm-5.3-flash.toml1661 bytes SHA7cdb7a1cfea9ab7e7c3e3392f0fdad0ac9c3f9c92e2f71a2d109788c5d02f843
api providers/zai/models/glm-5.3-flash.toml551 bytes SHA84812c0777b2a1c36f2c83f6edf00b35121c89a6fc37add9b865d528190cb955
coding providers/zai-coding-plan/models/glm-5.3-flash.toml437 bytes SHA2897ea37e74bb211bf351d2ccf1e653a23ac1c065f9635c82b87ea8d04c9e71a
Those three are genuine original upstream https://raw.githubusercontent.com/anomalyco/models.dev/f014f106dd414d575de2d0160d91267e2e7cb119/ inputs, not Creatidy mirror replacements or claims of upstream HEAD.
https://docs.z.ai/devpack/overview.md7150 bytes SHAa0c5d33dd02c80cc9e1d4635f7a744725dbfdac32960ba8b587c4fdcf1ca5183
https://docs.z.ai/devpack/notice/event-glm-5.3-flash.md1947 bytes SHAd0805c7fb3e27d72a049b380426a96714edbe89f32f79a5a11a118a67f2c18f9
https://docs.z.ai/api-reference/llm/chat-completion.md42517 bytes SHA983acca8656acdc9507778b72a8f4f5085c461aaaf52d23863d7203dd5187878
https://docs.z.ai/devpack/notice/usage-revision.md8178 bytes SHA9c58e3ff3923e18ab953d95f923ddba57472ad8b12043fb1918617072349caf9

No real positive adoption is claimed: actual zai.SCOPE channel=null and adapter-level configuration; subjects lack native configuration/explicit effort; producer Observation.fresh_until remains unknown; native meanings are not guessed into input/output allowances. These are independently inspected actual production code/contract facts also identified by completed MI19 installed acceptance. Earliest independently executable remedy: MI curator review changed official pricing bounds/schema against actual sources, then publish a COMPLETE compatible generation; source/curator supply evidenced exact native applicability and explicit freshness/meaning basis, Router owner review exact association. This requires neither MI waiting on new Router APIs nor invented values, synthetic acceptance, live calls or cross-repo changes. Original-code/source data rights remain separate; no raw official prose copied to repo.

Current implementation has actual controlled selector hard-constraint/route/no-route/pinned allow/refuse tests and exact-time/reference snapshot/replay. Default/bootstrap compatibility tests pass; controlled evidence is explicitly NOT real-source acceptance. Full gates and independent review pending.

Selected direct owner follow-up; base4162f6fa9f774beaf6e92d86b7ebc92f306da4bd, branch issue-222-active-mi, same designated clean checkout before edits. D082 direct approval2026-10-26T22:57:22Z recorded in decisions; #176/MI19 remain closed. Scope/threat: explicit exact-reference/time-bound MI policy intersects existing known token ceilings and narrows existing selection/resource/pinned-admission gates, preserving defaults/auth/private policy/ratings. No new catalog/producer/DB/service, live inference/production activation, external writes or dependency changes. Reuse pinned MI d65891668b7e79f7b666c021f02a1b4bf8c4ca9c; latest MI develop8f572c332db8290b5dad9e03f5b0f960271a8349 contains completed19 receipt, not changed producer semantics. Default10 fresh whole-PR reviews, none dispatched yet for222; no176 count reuse/exception. Technical recovery at most3 materially distinct approaches/obstacle and120min; no complexity expansion. ACTUAL public-source investigation 2026-10-26T22:59:29.062118Z used existing MI acquisition.fetch with its original source allowlist/byte bounds and sanitized credential-free environment, no redirects, model calls, files or publication. The actual eight-source generation was incomplete: pricing https://docs.z.ai/guides/overview/pricing.md exceeded declared2620-byte bound. A separate diagnostic-only larger bounded request (not producer normalization/input/policy) then returned HTTP500/source-retrieval-failed; no blind retry or widened producer config. Seven successful actual reads: - catalog models/zhipuai/glm-5.3-flash.toml1661 bytes SHA7cdb7a1cfea9ab7e7c3e3392f0fdad0ac9c3f9c92e2f71a2d109788c5d02f843 - api providers/zai/models/glm-5.3-flash.toml551 bytes SHA84812c0777b2a1c36f2c83f6edf00b35121c89a6fc37add9b865d528190cb955 - coding providers/zai-coding-plan/models/glm-5.3-flash.toml437 bytes SHA2897ea37e74bb211bf351d2ccf1e653a23ac1c065f9635c82b87ea8d04c9e71a Those three are genuine original upstream https://raw.githubusercontent.com/anomalyco/models.dev/f014f106dd414d575de2d0160d91267e2e7cb119/ inputs, not Creatidy mirror replacements or claims of upstream HEAD. - https://docs.z.ai/devpack/overview.md7150 bytes SHAa0c5d33dd02c80cc9e1d4635f7a744725dbfdac32960ba8b587c4fdcf1ca5183 - https://docs.z.ai/devpack/notice/event-glm-5.3-flash.md1947 bytes SHAd0805c7fb3e27d72a049b380426a96714edbe89f32f79a5a11a118a67f2c18f9 - https://docs.z.ai/api-reference/llm/chat-completion.md42517 bytes SHA983acca8656acdc9507778b72a8f4f5085c461aaaf52d23863d7203dd5187878 - https://docs.z.ai/devpack/notice/usage-revision.md8178 bytes SHA9c58e3ff3923e18ab953d95f923ddba57472ad8b12043fb1918617072349caf9 No real positive adoption is claimed: actual zai.SCOPE channel=null and adapter-level configuration; subjects lack native configuration/explicit effort; producer Observation.fresh_until remains unknown; native meanings are not guessed into input/output allowances. These are independently inspected actual production code/contract facts also identified by completed MI19 installed acceptance. Earliest independently executable remedy: MI curator review changed official pricing bounds/schema against actual sources, then publish a COMPLETE compatible generation; source/curator supply evidenced exact native applicability and explicit freshness/meaning basis, Router owner review exact association. This requires neither MI waiting on new Router APIs nor invented values, synthetic acceptance, live calls or cross-repo changes. Original-code/source data rights remain separate; no raw official prose copied to repo. Current implementation has actual controlled selector hard-constraint/route/no-route/pinned allow/refuse tests and exact-time/reference snapshot/replay. Default/bootstrap compatibility tests pass; controlled evidence is explicitly NOT real-source acceptance. Full gates and independent review pending.

adrian.tkacz referenced this issue from a commit

2026-10-26 23:30:24 +00:00

Apply approved opt-in MI evidence to selection and admission (#222)

kilo referenced this issue

2026-10-26 23:30:38 +00:00

Apply approved D-082 opt-in MI policy to selection and admission #223

kilo referenced this issue from a commit

2026-10-26 23:34:49 +00:00

Merge pull request #223: approved opt-in MI selection and admission

kilo commented

2026-10-26 23:36:09 +00:00

Author

Member

ACCEPTED IMPLEMENTATION integrated via PR223 BioMedical-IT/scarcity-router#223 as merge4a182affa4775a4a38b47860ad7622a099c56c4a at2026-10-26T23:34:47Z. MCP merged=true; fetched develop and actual parents match approved base4162f6fa9f774beaf6e92d86b7ebc92f306da4bd / HEADbddd71b24988e916122f647ec9fa0278b9d15706. Ancestry passes; reviewed and integrated trees exactly equal09c2b246533e6eeafb7fdedd9a4303ccb0862d32. Same checkout now clean on exact currentdevelop; feature branch/commit retained, no direct develop push.

Criteria1-6 verified: D082 direct owner approval recorded; explicit exact-cut/time-bound MIAdmission now affects actual selector qualification, route/no-route and exact-pin admission using conservative known-ceiling intersections plus existing policy/resource gates. Defaults/explanation/bootstrap/private auth/capacity/quality/entitlement/execution-identity remain intact; unknown never fills a guarantee; exact channel/effort controls still required; revocation/conflict/freshness/history preserved through reused MI contracts. Retained original cut/full evaluation context/result/manifest and accepted utilization envelope bind actual decisions. Historical snapshots cannot authorize later instants. Controlled tests explicitly prove limit-bound qualification, route rejection, pinned allow/refuse, output ceiling, auth/channel/effort refusal, unknown/stale/future/conflict/withdrawal, exact-reference refresh/no auto-approval, replay/expiry and bootstrap preservation.

Full sanitized make check3057 tests OK/18 skips and managed type0/0; explicit basedpyright0/0; offline canonical uv sync; package-check wheel/sdist/isolated installed interfaces; diff/staged whitespace pass.136 focused MI/application/route tests rerun on ACTUAL integrated develop passed. Fresh visible native whole-PR review1 APPROVE/findings[] at exact parents, separate session ses_e8571f327ffezZQITaIQSUvOKk; provenance/result in PR comment19069. Live retrieval was not repeated independently; installed producer absence independently verified, no positive real-source/production claim. Only1/10 review consumed, no history reset.

Real-source result remains negative, not a fictional activation: seven original upstream inputs fetched; pricing failed declared-size policy then separate bounded diagnostic failedHTTP500. Exact URLs/digests/time/complete-generation refusal in19056. Existing actual published adapter scope/subjects omit exact native channel/configuration/effort and explicit freshness; source-native meanings cannot be guessed into Router allowances. Current models.dev source advertises model identity/reasoning options/pricing, but none supplies current positive admission authority here. Earliest independently executable action belongs to MI producer/curator: review changed official input bounds/schema, produce a complete compatible cut and evidenced exact native applicability/freshness/meaning, then Router association review. No MI-to-Router circular prerequisite, synthetic substitute, external issue creation or MI/Kernel changes. Completed176/MI19 remain closed.

Closing this implemented and independently accepted follow-up does NOT claim real-source positive adoption, production activation, deployment/release/main or Daybreak. Those were not authorized; no service or second catalog/rater/producer/DB was created. Canonical Forgejo references preserved; only intentional genuine external upstream references used.

ACCEPTED IMPLEMENTATION integrated via PR223 https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/pulls/223 as merge4a182affa4775a4a38b47860ad7622a099c56c4a at2026-10-26T23:34:47Z. MCP merged=true; fetched develop and actual parents match approved base4162f6fa9f774beaf6e92d86b7ebc92f306da4bd / HEADbddd71b24988e916122f647ec9fa0278b9d15706. Ancestry passes; reviewed and integrated trees exactly equal09c2b246533e6eeafb7fdedd9a4303ccb0862d32. Same checkout now clean on exact currentdevelop; feature branch/commit retained, no direct develop push. Criteria1-6 verified: D082 direct owner approval recorded; explicit exact-cut/time-bound MIAdmission now affects actual selector qualification, route/no-route and exact-pin admission using conservative known-ceiling intersections plus existing policy/resource gates. Defaults/explanation/bootstrap/private auth/capacity/quality/entitlement/execution-identity remain intact; unknown never fills a guarantee; exact channel/effort controls still required; revocation/conflict/freshness/history preserved through reused MI contracts. Retained original cut/full evaluation context/result/manifest and accepted utilization envelope bind actual decisions. Historical snapshots cannot authorize later instants. Controlled tests explicitly prove limit-bound qualification, route rejection, pinned allow/refuse, output ceiling, auth/channel/effort refusal, unknown/stale/future/conflict/withdrawal, exact-reference refresh/no auto-approval, replay/expiry and bootstrap preservation. Full sanitized make check3057 tests OK/18 skips and managed type0/0; explicit basedpyright0/0; offline canonical uv sync; package-check wheel/sdist/isolated installed interfaces; diff/staged whitespace pass.136 focused MI/application/route tests rerun on ACTUAL integrated develop passed. Fresh visible native whole-PR review1 APPROVE/findings[] at exact parents, separate session ses_e8571f327ffezZQITaIQSUvOKk; provenance/result in PR comment19069. Live retrieval was not repeated independently; installed producer absence independently verified, no positive real-source/production claim. Only1/10 review consumed, no history reset. Real-source result remains negative, not a fictional activation: seven original upstream inputs fetched; pricing failed declared-size policy then separate bounded diagnostic failedHTTP500. Exact URLs/digests/time/complete-generation refusal in19056. Existing actual published adapter scope/subjects omit exact native channel/configuration/effort and explicit freshness; source-native meanings cannot be guessed into Router allowances. Current models.dev source advertises model identity/reasoning options/pricing, but none supplies current positive admission authority here. Earliest independently executable action belongs to MI producer/curator: review changed official input bounds/schema, produce a complete compatible cut and evidenced exact native applicability/freshness/meaning, then Router association review. No MI-to-Router circular prerequisite, synthetic substitute, external issue creation or MI/Kernel changes. Completed176/MI19 remain closed. Closing this implemented and independently accepted follow-up does NOT claim real-source positive adoption, production activation, deployment/release/main or Daybreak. Those were not authorized; no service or second catalog/rater/producer/DB was created. Canonical Forgejo references preserved; only intentional genuine external upstream references used.

kilo closed this issue

2026-10-26 23:36:14 +00:00

kilo referenced this issue from Creatidy/creatidy-kernel

2026-10-27 00:30:48 +00:00

[Kernel][G08] Serve authoritative state and reconnectable progress to CLI, Console and notifications #57

kilo referenced this issue from Creatidy/creatidy-kernel

2026-10-27 00:31:22 +00:00

[Kernel][G07] Deliver versioned private outcome and full-cost evidence export #58

kilo referenced this issue from Creatidy/creatidy-kernel

2026-10-27 00:31:31 +00:00

[Kernel][G06] Retain admitted knowledge snapshot and harness-evidence provenance #55

kilo referenced this issue from Creatidy/creatidy-kernel