[Kernel][G06] Retain admitted knowledge snapshot and harness-evidence provenance #55
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.
Depends on
#105 Deliver independent work, SCM, CI and knowledge drivers with a heterogeneous project path
Creatidy/creatidy-kernel
Reference
Creatidy/creatidy-kernel#55
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: P3
Type: optional integration.
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.P3 means optional capability expansion with a useful independent result under the integrated P0-P3 Priority Contract; delivered provenance is not demoted or redelivered. 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
Receive selected versioned MI/harness knowledge as attributed context without duplicating catalogue/ranking or creating authority.
Why
PR #101 already delivers utilized-reference provenance and must not be redelivered as missing work.
Scope
Preserve codec-v3 utilized reference and local-only labels; optional direct content/sidecar/cut interpretation and harness-interface evidence through #105's knowledge seam, only for supported producer semantics. MI #19 / SR #176 remain accepted explanation-only installed work.
Current producer correction: SR newer develop
4a182affa4775a4a38b47860ad7622a099c56c4a, #222/PR #223, integrates default-off D-082 opt-in MI admission. D-082 policy is not wholly unaccepted. This does not establish real-source positive adoption, all-scope source association or CK direct-content acceptance and does not expand this issue. The historical alignment cut's broader-policy caveat must not be read as denying that integrated bounded opt-in policy.Acceptance Criteria
Dependencies
#105 for new generic reader composition; exact existing MI publication/utilization contract and SR utilization only when that lane is used. No #52/#106/basic-coordination prerequisite in either direction. Owner-controlled expansion of sharing/active adoption remains a separate decision.
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.mdBioMedical-IT/scarcity-router@4a182affa4Historical Scope And Evidence
Goal
Owner: Kernel consumer. Preserve references to actually used MI knowledge/provenance supplied through Router decisions, and separately support justified direct harness-interface evidence without becoming an intelligence ranking/collection product. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 brief.
Why
The accepted result must explain which knowledge informed routing or harness compatibility without fabricating a snapshot identity. MI normally supplies Router, not a mandatory per-inference Kernel service; unavailable MI alone should not terminate an already authorized Attempt.
Current Evidence
Kernel
eb4f4a2956has ContextPackage manifests and canonical decision provenance in Allocation but no MI publication consumer. #7 excludes full context/telemetry; #11 recommendation-only. MI develop fb7299810fdc4612d4e0559465faef571662c6ef integrates #9/PR #10 evidence/knowledge/effective projection proof, not a publication wire schema. Actual producer MI #13 defines future publication/conformance and #14 defines mapping ownership; Router #176 is consumer work, not implemented integration.Scope
Consume producer-approved publication references and associated completeness/version/provenance/unknown semantics through the Router public result. Persist utilized knowledge at preparation and retain it across restart/candidate/export. If directly reading MI for harness API evidence, keep assertion strength/version/time/licensing distinct from local observed capability and authority. Do not invent shared schema before producer-consumer agreement.
Acceptance Criteria
Reuse
Retain ContextPackage/Allocation/provenance and content-addressed artifacts; adopt MI #13 publication and Router #176 consumer contract only after exact revision/files/rights/semantic/negative/security/dependency/maintenance proof. Reuse MI temporal distinctions, not its proof Python layout as a permanent wire API. No crawler, score, ontology or direct benchmark-to-model choice.
Dependencies And Priority
Contract integration after MI #13 publication and Router #176 admitted-result provenance, alongside Kernel #51 requirements/#52 route and #47 harness evidence. #14 coordinates mapping ownership. This registered consumer issue does not duplicate MI production or Router consumption; prioritize before claiming explainable end-to-end route evidence.
Constraints And Permissions
No private balances/quota collection, local ranking, authority from snapshots, mandatory remote MI lookup, automatic publication or state sharing. Offline contract proof needs no inference; live producer/service access and direct harness probes need separately scoped access/inference where applicable. Contested freshness/withdrawal policy needs the relevant owner.
Links
Non-Goals
No MI publication, Router catalog migration or ranking implementation inside Kernel; no live inference authority.
Producer semantics clarification fetched from actual MI #13 comment Creatidy/model-intelligence#13 (comment): conformance must freeze the evidence cut and evaluation semantics, not a guessed current-view digest. Existing knowledge(evidence, at) is not historical knowledge reconstruction; effective_at does not itself filter stale observations; fresh_until=None is not proved freshness. Preserve exact utilized reference/input cut and unknown freshness in Kernel without changing MI proof semantics, inventing global TTL or querying today's mutable evidence during replay. Publication completeness and licensed-source production remain MI #13/#15, admission/freshness policy Router #176, Kernel retention this issue. Optional operational sharing MI #17 is not a prerequisite for local execution or authorized active Attempt recovery.
Selected under the resumed
/loopafter fresh queue/producer verification. Bounded offline utilized-reference consumer proposed in PR #101 (Refs #55; keep this issue open).Router #176 is accepted with its actual consumer merged at
4162f6fa…consuming the MI publicationd658916…; Router's own issue names Kernel #55 as the separate downstream utilized-reference consumer. This delivery retains and validates the exactmi_utilizationreference (model_intelligence/urn:mi:utilization:sha256:<64hex>/mi.utilization-working/1) from the public selection envelope, binds it immutably to the Attempt allocation (codec v3; v1/v2 bytes unchanged), distinguishes corrupt grammar (refusal) from unsupported producer versions (explicit retention), exports explicitnot_retained/utilized/unsupported_versionstates with provenance-only/local-only labels, and negative-tests that the reference grants no runtime authority. Restart stability is asserted end to end through the reference composition, including router-outage and changed-decision recovery.Remaining open scope for this issue: direct MI harness-interface evidence reads (the AC4 conditional clause), any utilization sidecar/cut decoding, freshness/withdrawal semantics beyond the reference grammar, and live producer access. Full route retention (#52) stays separately gated by the recorded Kilo/Router main-path incompatibility.
Bounded utilized-reference consumer integrated in PR #101 (Refs #55; issue deliberately stays open). Supported normal merge produced
038da8be9c4d07e3ccc92c107862125f979a5c47with exact parents basef4d86ea0a8e1b048d186fae01d49bb2283fc99d6and approved headfdc2aa98a7922d3c8610eac1dc3edfb17c601f8b; develop advanced from the approved base, the approved head is its ancestor, and the integrated tree is byte-identical to the reviewed head. CI succeeded on the exact head (#3238, 2m26s).Review ledger for this delivery: ordinal 1 infrastructure failure (subagent usage limit, no verdict), ordinal 2 COMMENT infrastructure (full independent source verification, zero findings; gates not executed because the reviewer's improvised command variants did not match the exact-string allowlist), ordinal 3 fresh APPROVE with empty findings — independently executed
make check(1503 passed/85 skipped/106 subtests) andmake package-check, plus producer-contract verification at Router4162f6fand MId658916including Apache-2.0 license checks.Delivered:
mi_utilizationreference validation with corrupt-grammar refusal and explicitunsupported_versionretention; allocation codec v3 immutable Attempt-bound retention (v1/v2 bytes unchanged); explicitnot_retained/utilized/unsupported_versionexport states with provenance-only/local-only labels; provenance-only no-authorory negative tests; end-to-end restart stability through the reference composition including router-outage and changed-decision recovery.Remaining open scope on this issue: direct MI harness-interface evidence reads (AC4 conditional clause), utilization sidecar/cut decoding, contested freshness/withdrawal policy (owner-gated per Constraints), and any live producer access.