Deliver cross-product overview and exact Kernel task evidence drill-down #4

Open
opened 2026-10-04 23:02:40 +00:00 by kilo · 1 comment
Member

Goal

Owner: Console views/navigation. Answer what works, why and whether owner action is needed, with exact task outcome lineage.

Why / Current Evidence

Operators should not read logs or fabricated progress to understand work. Console seed d6468f3 contains no operational UI. Kernel eb4f4a2956712bfaf39a3271e1523e7f77a91e26 has bounded tasks/internal evidence, not delivered concurrent Console view; alignment #46/PR63 is not capability proof. Source sections 3-6,12; G01/G02/G03/G04/G05/G07/G08/G10/G11.

Scope / Non-Goals

Overview prioritizing consequential blockers/uncertainty; intent/scope -> attempt -> harness/session -> routing -> candidate SHA -> verification/reviewer/verdict/iteration -> outcome. Show exact workspace host/identity and supported safe inspection. No scheduling/intake classification/review engine, invented hidden reasoning or token-based completion percentage.

Acceptance Criteria

  • Router-only useful and unconfigured Kernel/MI not outages; empty/denied/unsupported/disconnected/stale cases distinct per producer.
  • Exact namespaced IDs and source revisions available through progressive disclosure; missing correlation/evidence labeled unavailable, no join by label/time.
  • Recorded requirements/policy explain choices; historical PR receipt is not current merge/PR state; stale verdict cannot imply accepted candidate.
  • Remote browser does not pretend to own the task filesystem; unsupported attach unavailable and no shell/file URL shortcut.
  • Browser close/reconnect preserves producer lifetime and never grants control; operational progress and diagnostic traces distinct from acceptance.

Constraints

Private task metadata not exported by default; safe text/link rendering, version mismatches explicit, view/settings migrations rebuildable. Reuse existing producer evidence serializers and Forgejo/harness links; no duplicate diff/review UI. Priority P2 after supported reads/projections and producer evidence dependencies. Actual product/browser proof needs separately authorized service access; no task execution or inference authorized by issue registration.

Parent #1; Console read/projection/a11y/navigation issues. Kernel Creatidy/creatidy-kernel#47 (harness), /issues/48 (intake), /issues/54 (review), /issues/55 (references), /issues/57 (views), /issues/58 (outcomes); Router BioMedical-IT/scarcity-router#183.

## Goal Owner: Console views/navigation. Answer what works, why and whether owner action is needed, with exact task outcome lineage. ## Why / Current Evidence Operators should not read logs or fabricated progress to understand work. Console seed d6468f3 contains no operational UI. Kernel eb4f4a2956712bfaf39a3271e1523e7f77a91e26 has bounded tasks/internal evidence, not delivered concurrent Console view; alignment #46/PR63 is not capability proof. Source sections 3-6,12; G01/G02/G03/G04/G05/G07/G08/G10/G11. ## Scope / Non-Goals Overview prioritizing consequential blockers/uncertainty; intent/scope -> attempt -> harness/session -> routing -> candidate SHA -> verification/reviewer/verdict/iteration -> outcome. Show exact workspace host/identity and supported safe inspection. No scheduling/intake classification/review engine, invented hidden reasoning or token-based completion percentage. ## Acceptance Criteria - Router-only useful and unconfigured Kernel/MI not outages; empty/denied/unsupported/disconnected/stale cases distinct per producer. - Exact namespaced IDs and source revisions available through progressive disclosure; missing correlation/evidence labeled unavailable, no join by label/time. - Recorded requirements/policy explain choices; historical PR receipt is not current merge/PR state; stale verdict cannot imply accepted candidate. - Remote browser does not pretend to own the task filesystem; unsupported attach unavailable and no shell/file URL shortcut. - Browser close/reconnect preserves producer lifetime and never grants control; operational progress and diagnostic traces distinct from acceptance. ## Constraints Private task metadata not exported by default; safe text/link rendering, version mismatches explicit, view/settings migrations rebuildable. Reuse existing producer evidence serializers and Forgejo/harness links; no duplicate diff/review UI. Priority P2 after supported reads/projections and producer evidence dependencies. Actual product/browser proof needs separately authorized service access; no task execution or inference authorized by issue registration. ## Links / Dependencies Parent #1; Console read/projection/a11y/navigation issues. Kernel https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/47 (harness), /issues/48 (intake), /issues/54 (review), /issues/55 (references), /issues/57 (views), /issues/58 (outcomes); Router https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/183.
Author
Member

Dependency clarification from completed canonical Kernel inspection: task intake is Kernel #49, not #48. #48 owns lifecycle/deadline repair and remains a relevant failure-state dependency; #47/#53 own harness proof/integration. Additional explicit dependencies: Kernel #51 requirements, #52 executable route identity, #56 task budget, #59 concurrency and #60 composed acceptance. Console own links: #2 reads/auth, #3 projections, #8 navigation, #10 accessibility and #12 validation. All references are registered work, not shipped capabilities. This corrects the shorthand intake label in the initial body.

Dependency clarification from completed canonical Kernel inspection: task intake is Kernel #49, not #48. #48 owns lifecycle/deadline repair and remains a relevant failure-state dependency; #47/#53 own harness proof/integration. Additional explicit dependencies: Kernel #51 requirements, #52 executable route identity, #56 task budget, #59 concurrency and #60 composed acceptance. Console own links: #2 reads/auth, #3 projections, #8 navigation, #10 accessibility and #12 validation. All references are registered work, not shipped capabilities. This corrects the shorthand intake label in the initial body.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Creatidy/creatidy-console#4
No description provided.