Inspect referenced MI knowledge snapshots, validity and conflicts #6
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#3 Implement resilient snapshot and progress projections with honest reconnect gaps
Creatidy/creatidy-console
Reference
Creatidy/creatidy-console#6
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?
Goal
Owner: Console knowledge view. Explain the exact evidence a recorded decision used, preserving uncertainty and source rights. MI owns and publishes the initial versioned operator/export contract; Console supplies consumer requirements and validates/adopts it.
Why / Historical Evidence
Public knowledge is not live account entitlement or routing advice. Console seed
d6468f3has no MI client. MI fb7299810fdc4612d4e0559465faef571662c6ef integrates synthetic temporal/provenance/conflict/delta proof; no published snapshot or replay feed at that inspected revision. effective_at does not enforce freshness and endpoint projection delta is not causal history. Source sections 3,4,6,7,9; G06/G08/G10/G13. This is the historical intake evidence, not a refreshed claim about current MI implementation. Console #2's completed design inventory remains historical evidence, not approval of a browser topology or a gate on defining the initial MI contract.Scope / Non-Goals
Exact decision-referenced snapshot/evidence cut, sources/acquisition/validity, stale/unknown/conflicting/withdrawn/future states and meaningful changes. No catalog, crawler, calibration, conflict winner, entitlement or new model recommendation. No competing Console-owned MI schema.
Producer-First Contract and Consumer Conformance
Owner decision, 2026-10-08: #6 (comment).
Acceptance Criteria
The following existing semantics remain consumer requirements for contract validation and actual #6 integration; contract-only conformance does not complete the adapter/UI feature.
Constraints
Safe untrusted source rendering/links, privacy/redaction and lawful redistribution; unsupported authority states fail closed, snapshot compatibility/migrations tested. Reuse MI producer conformance cases, not serialize its Python proof layout as invented JSON. Priority P2 following publication and real-source value; separately authorized service/artifact access, no inference.
This dependency/documentation correction does not authorize implementing #6, introducing a BFF, selecting browser topology, accessing live/private data, weakening security or claiming installed acceptance.
Links / Dependencies
Parent #1. Required direction: MI Creatidy/model-intelligence#16 initial contract -> contract-level consumer conformance/adoption -> Console #6 adapter/UI integration. There is no completion dependency from MI #16 back to Console #6. Cross-repository dependencies are recorded by links, not same-repository native edges.
Downstream integration retains Console #3 projection infrastructure, the actual supported read/auth gate inventoried by #2 (not merely its closed state), #10 accessible views/semantic agreement and #12 browser/security/conformance and separately authorized installed acceptance. Preserve the existing native #6 -> #3 prerequisite; it does not block contract-only definition/validation.
Other applicable producer/integration gates remain MI Creatidy/model-intelligence#12, /issues/13, /issues/14 and /issues/18 (including actual publication/distribution); Router BioMedical-IT/scarcity-router#176; Kernel Creatidy/creatidy-kernel#55. These gate the relevant composed/operational integration, not completion of Console components before the initial MI contract can be defined or validated.
Owner Dependency Decision, 2026-10-08
The owner explicitly authorizes this bounded dependency/documentation correction: MI, as producer, owns and publishes the initial versioned operator/export contract. Console, as consumer, defines requirements and validates/adopts that contract.
MI #16 is upstream of Console #6. It does not require Console #6, a working Console adapter/UI, or completed Console projection/browser/installed acceptance to define and validate its initial contract. The existing Console semantic requirements are consumer input, not a competing Console-owned MI schema. Contract-level producer-consumer conformance may use offline, version-pinned portable fixtures; it must be described as such, not as an exercised Console adapter or live/browser/installed receipt.
The graph is producer-first: MI #16 contract publication -> contract-level consumer conformance/adoption -> Console #6 adapter/UI integration. Real integration retains its applicable Console #3 projections, supported read/auth boundary from #2, #10/#12 view/browser/security acceptance, MI publication/distribution (#13/#18), Router #176, Kernel #55 and authorized installed acceptance gates. None of those completed downstream components is a prerequisite merely to define or validate the initial MI contract.
Missing or incompatible fields require a concrete Console consumer requirement and a requested versioned MI producer change, never silent reinterpretation or a parallel Console schema. The historical #2 design inventory and exact revision evidence remain unchanged; this decision is additional sequencing/ownership authority, not new implementation evidence.
This resolves the Console-side receiver/contract ambiguity recorded in Creatidy/model-intelligence#16 (comment) without modifying MI records or implementing either feature. Scope is issue #6 and docs/contracts.md/docs/roadmap.md through the existing develop PR, full-validation and independent exact-HEAD-review workflow. No duplicate task, BFF, browser topology, weakened security, live integration, merge, release or deployment is authorized.
Bounded dependency/documentation correction is delivered in #25 (Refs #6), not implementation/completion of the knowledge view. Issue body and docs/contracts.md/docs/roadmap.md now consistently record MI #16 -> portable contract-level consumer conformance/adoption -> Console #6 adapter/UI integration, with existing semantics, #2 historical inventory and downstream gates retained.
Base/merge-base
6a254921a62b4a81c51dcc2c414692d5c22cf35c; clean pushed HEAD1277ab69157000a0fa84b93ba3123b3e8aa50471.make installand offlinemake checkpassed (format, Markdown/links/secrets, TypeScript, 21 tests, temporary static artifact/license checks); working/staged/full committed diff whitespace checks passed. Independent exact-HEAD review follows. No actual contract fixtures, adapter/UI, browser topology/BFF or installed acceptance were implemented or exercised. #6 stays open and the standalone PR stays unmerged; no duplicate task or cross-repository mutation.Dependency/documentation correction in #25 is READY_TO_MERGE, unmerged. Fresh native independent whole-PR review ordinal 1/10 returned APPROVE with no findings at HEAD
1277ab69157000a0fa84b93ba3123b3e8aa50471, base/merge-base6a254921a62b4a81c51dcc2c414692d5c22cf35c; no remediation commits. Reviewer independently checked the records/full delta/historical pinned MI evidence and reran offlinemake checksuccessfully (21 tests plus all documentation, type, secret and temporary artifact/license gates). Exact-HEAD CI #2392 also passed: https://forgejo.creatidy.com/Creatidy/creatidy-console/actions/runs/17.Final canonical MCP/Git currentness matches those reviewed SHAs and the checkout is clean. The acyclic Console record is MI #16 initial producer-owned contract -> portable contract-level consumer conformance/adoption -> #6 adapter/UI integration with its downstream gates. #6 stays open because the knowledge-view feature is not implemented; no actual contract fixture, browser/installed acceptance, BFF/topology selection, new task or other-repository mutation occurred.