docs: align shared harness, routing and observability architecture (#46) #63
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/creatidy-kernel!63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-46-shared-architecture"
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?
Delivery State
REVIEW_INFRASTRUCTURE_BLOCKED: not ready for owner merge. One documentation-only PR to develop, OPEN and unmerged. No functional gap is closed, no product task/inference, merge/release/deploy or main change.
Refs #46. Canonical/frozen base:
eb4f4a2956712bfaf39a3271e1523e7f77a91e26. Final published HEAD:f3dd9f85e620cb9e6c354c3aeb3988ec12f0159b. Two focused documentation commits; clean worktree. Earliera90920avalidation is historical, not final-head evidence.Changes And Source
17 English documentation/context files only; no product schemas/src/tests/dependencies/tooling/workflow changes. Add ADR 0007 for agreed Kernel/Router/MI/Console ownership, controlled existing harness and Router gateway target, no invented endpoint/payload/flag/protocol or service deployment. Preserve old ADR decisions with linked extensions, dated A0/K1-K8 evidence and explicit limitations.
README, owning target/contracts/roadmap/reuse/migration/threat/delivery, SECURITY/CONTRIBUTING/AGENTS and short development rules separate Agreed / revision-Verified / Proposed clarification / To prove. Correct private-operator/#34 rollout and task-vs-reference deadline/cancel/export claims.
.kiloremains development context, not product execution.Source: shared system architecture v1.0 2026-10-04; supplied filename/SHA-256 and relevant section range retained in ADR. Full file not found, owner brief available; no locally verified digest or missing subsection/technical decision fabricated. Reuse candidates retain actual-source/license/service/rights distinction; version-pinned bibliography and unrun conformance obligations are on #47, no adoption approval.
Registered G01-G13 Coverage
Actual OPEN Kernel #47-#62 are 16 independently receivable proof, repair, integration and installed-acceptance tasks, not selected execution. The complete requirement -> owner -> revision/path/test -> correction -> existing-AC comparison -> actual issue matrix, dependencies/priority/closure and necessary owner decisions are in
docs/architecture/successor.mdand #46 report.#47 harness/backend proof; #48 lifetime/envelope/cancel/freshness; #49 approved intake; #50 safe verification/isolation; #51 task requirements; #52 executable-route/identity consumer; #53 proved adapter/session; #54 durable product review/remediation; #55 frozen MI references; #56 whole-task costs/budgets/retries; #57 state/events/CLI/notifications; #58 private outcome export; #59 concurrent workspace/manual-edit ownership; #60 installed end-to-end reception; #61 host cache/locks/cleanup/source dispatch identity; #62 contract/state/ciphertext/install/platform migration.
Existing narrower #4-#13/#31/#32/#37/#42/#44 are evidence, not broadened closure. Existing #44 received only link/integrated-status correction: #143/#166 belong to Router. No implementation issue closed, known work hidden in DEFER or giant fix-everything issue, or other-product object modified.
Urgent Deviations Remain
Each has observable negative/recovery closure, not documentation approval or unrelated green tests. No READY_FOR_LIVE_TASK/product-complete claim.
Cross-Product Reception
Full actual producer AC were read and compared, then indexes rechecked once. Router #174/#178/#179/#180/#181 precede affected #52/#53 receipt; #165 cancellation remains explicit. #49 approved task meaning plus Router #175/MI #14 agreement precedes #51. MI #13 publication -> Router #176 consumption -> Kernel #55 retained evidence-cut/evaluation reference; MI proof is not published integration. Router #184 call facts feed Kernel #56; Kernel #58 -> optional Router #177, MI #17 sharing is NOT local-path prerequisite. Router #183/MI #16 serve their own facts, never replace Kernel state. Router #185/#186 and MI #18/#19 do not prove Kernel ciphertext/platform reception.
Final discovery found actual Console Creatidy/creatidy-console#1 bootstrap. Its documentation/gate/backlog AC is not a dedicated snapshot/event/command consumer receipt; Kernel #57 must receive that contract, no direct SQL/client scheduler/ranking/permission authority. Late reference is the second commit, same PR, no Console writes.
Exact Final-HEAD Validation
At
f3dd9f85e620cb9e6c354c3aeb3988ec12f0159b:make check: PASS, 966 tests in 116.83s; locked resolution, format/lint, basedpyright 0 errors/warnings, inward imports, secret scan no findings, git diff --check.make package-check: PASS; reproducible wheel/sdist rebuild, isolated installed offline CLI/replay/export.a90920a. Per-job API returned 404; detailed CI command/log output not independently available, only overall metadata success claimed.Unchanged command frontmatter literal YAML syntax passed; the Kilo edit hook's 'No context found for instance' does not establish client command rediscovery. Native link_pr helper rejects Forgejo URLs, while canonical MCP PR creation/readback succeeded. Neither was worked around by config/permission edits.
Required Independent Review Ledger
Scope remains WHOLE exact-final PR + actual G01-G13 registration matrix/backlog completeness, source/target/status distinctions, security/authority/migration/reuse and cross-product claims. Native /deliver-issue requires a FRESH Router scarcity_select decision, exact routed provider/model/variant and independently verified Agent Manager resolution. Security-sensitive architecture floor L4, capability minima 5/5/5 is retained, no author confidence substitution.
No scarcity_select tool is advertised here; general and targeted MCP discovery offered no usable routing interface. No ad-hoc REST, product call, permission/config change, guessed reviewer or other-session evidence reuse.
Fresh routed whole-PR and backlog review at final
f3dd9f85e620cb9e6c354c3aeb3988ec12f0159bin an authorized environment exposing scarcity_select is the concrete missing acceptance prerequisite before owner merge. This session neither changes that environment nor introduces a review controller/manual result relay. Green checks and mergeable metadata are not review approval, live readiness or functional closure.Frozen-HEAD Validation And Review Ledger
Canonical base
eb4f4a2956; published/final HEADa90920ae91, unchanged. Branch/status clean; 17 documentation/context files only, no product/tests/dependencies/tooling/workflow changes.After publication, exact-HEAD reruns completed:
make check: PASS; 966 tests in 128.12s, basedpyright 0 errors/warnings, locked deps/format/lint/inward imports, secret scan no findings and git diff --check.make package-check: PASS; reproducible sdist/wheel rebuild, isolated install and offline CLI replay/export.git diff --checkand documentation-only branch paths: PASS.Canonical CI metadata: SUCCESS, exact same HEAD, run 2197 / run number 79: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/79. Per-job listing returned 404, so detailed job/log output was unavailable; individual CI command outputs are not claimed. Local make audit was not run because no dependency/tooling/complete-local-CI gate change was selected.
Counterpart recheck performed once before handoff against canonical Router/MI indexes, after actual relevant bodies/AC had been fetched. All producer links used remain actual open tasks. MI #13/#14/#17/#18/#19 and Router #174-#186 relevant slices are producer-owned obligations, not implementation receipts. No other repo object was changed. #46 now holds the actual registration/matrix/priority/dependency report; bibliography candidate evidence is on #47, not an adoption claim.
Independent review remains NOT_RUN / REVIEW_INFRASTRUCTURE_BLOCKED. The required scarcity_select tool is absent from advertised tools; resource/template discovery has no usable Router interface. No fresh Router decision or Agent Manager reviewer launch/resolution exists. Security-sensitive architecture review floor is retained, not bypassed. Substantive verdict NONE; reviewed HEAD NONE; formal review list is empty; remediation 0/10 and not reset. Audits and author checks are not independent review. No owner merge readiness is asserted despite green checks and mergeable metadata.
No implementation, real product task/inference, secret/service/cost-policy/permission/branch-protection changes, main modification or merge/release/deploy occurred. No functional gap closed. Required next acceptance is fresh native routed whole-PR + backlog-completeness review at this exact HEAD in an authorized environment exposing scarcity_select; no new controller or manual reviewer-result relaying is introduced.
Final acceptance ledger supersedes earlier
a90920avalidation: final HEADf3dd9f85e6, baseeb4f4a2956, same PR/open/unmerged. Late Console#1 bootstrap discovery is linked in roadmap and #57, not claimed as consumer conformance. No other repo writes.Repeated final-head make check PASS (966 tests, 116.83s; all repo-owned gates) and make package-check PASS (reproducible installed offline distribution). Canonical CI run2198/number80 SUCCESS for same exact final SHA: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/80 . Working tree clean, two focused docs commits, 17 docs/context paths only. Job API404 limits detailed CI logs; no local audit or live behavior claim.
Required whole-PR + actual G01-G13 backlog review is still NOT_RUN / REVIEW_INFRASTRUCTURE_BLOCKED due to missing advertised scarcity_select. No routed decision/dispatch/resolution, substantive verdict/reviewed HEAD or formal review. Remediation0/10 unchanged. Prior/author/research evidence is not an independent review of this new HEAD. Before owner merge obtain fresh exact-final-head native review in a sanctioned environment with that tool; no guessed model, permission workaround, new review controller or manual result relay. No functional gap closed, product inference/task or merge/deploy/release/main change.
Terminology Remediation Delta
Owner-requested correction following independent review of
f3dd9f85e6. New published HEAD:96a3700b2a; unchanged canonical baseeb4f4a2956. Same PR, open/unmerged; no history rewrite. This new HEAD is for independent delta review, not an approval claim.Only changed file relative to the reviewed HEAD: docs/adr/0007-shared-harness-routing-observability.md, four insertions/two deletions in the product-identity paragraph. It now directly states Creatidy Kernel is the orchestration/control-plane product, Scarcity Router is the resource-routing product, public repository identifiers stay unchanged, and no additional router product/repository or Kernel rename is introduced. The erroneous interpretation is removed, not retained as a historical note.
The owner-required exact-literal Git search has zero current-tree matches (no output, expected exit1), both after edit and at published HEAD. A whole-repository local content search originally found only this ADR occurrence. Current issue #46 and PR #63 titles/descriptions plus 3/2 comments; all 16 #47-#62 titles/descriptions plus 9 comments; and task-owned #44 comment14085 were audited: no obsolete-name matches, so no existing Forgejo bodies/comments needed terminology edits. Comment totals match fetched metadata; numbered pagination repeated page1, so #47-#62 audit used matching counts and terminal since-cursor queries returning empty to verify completeness. No unrelated historical records or immutable commits changed.
Local validation after the correction: make check PASS (966 tests in107.65s, typing0 errors/warnings, all owned gates); make package-check PASS (reproducible wheel/sdist and isolated offline installed CLI); git diff --check PASS; focused repository/boundary guards6 passed. Clean one-file published delta verified. Canonical CI run2200/number81 SUCCESS with metadata-confirmed EXACT
96a3700b2a: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/81 . No result inferred from older CI.One owner-requested review-remediation cycle is recorded (1/10 cumulative, no reset). No functional G01-G13 work, tests/schema/dependency changes, product inference, architecture redesign, merge/release/deploy or main modification. Earlier delivery/check records refer to their old SHAs; this correction does not rewrite them or claim a verdict for the new HEAD.