Skip to content

epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184

Open
63 of 100 issues completed

Description

@dezren39

Summary

Epic for the PM stack coherence program, commissioned by Drew's full-stack review (2026-10-26 ~22:35 CDT). Drew owns the verdict this epic answers: the stack's beginnings exist, but it is "not easy to navigate or particularly coherent… the data is stale or only partially adopted." His requirements (the yardstick for every child):

  • ONE single URL, mobile or desktop, to see ALL projects
  • On it: quotas & usage; page health; issues that need his attention
  • REMEDIATE / respond / basic triage from there — not read-only
  • Queued + in-progress work clear: what would be picked up NEXT, what's being worked on, what's BLOCKED, what was DONE recently
  • Hierarchy with rollups: roadmap item > epic > issue (not just issue level)
  • The glued-together topology (services, ports, Kaneo vs the rest) documented ON the dashboard

Headline evidence from the review (2026-10-26 ~22:40 CDT, laptop + gh, cross-checked)

  • /attention shows "Needs Drew (0)" while the published orchestration.json carries 11 NEEDS DREW items — tier source rejected (fix(aggregator/orchestrator): orchestration section rejected — provenance is an object, isOrchestrationSection requires a string #1110) with NO indication on the page
  • Every footer falsely claims the orchestrator "has not published a section" (it publishes hourly; the aggregator rejects it)
  • Board: 95 of 107 cards are Done — a completion log again
  • Items layer: "fixtures for 172 ref(s) outside the pool" — fixture states wear live badges
  • Pool: 139 items, 17 with no Area; Grist 23 rows vs 16 Project epics (spec wants 1:1)
  • No health page, no staleness alerting, no triage write actions beyond comments (comments store still holds only the 3 demo comments from Oct 25)
  • All services themselves were UP at review (aggregator/Kaneo/Postgres/Pad/Grist containers healthy; ready-for-agent, tunnel live) — the gap is coherence, not uptime

Children — information architecture & front door

Children — data freshness, honesty, adoption

Children — health & observability

Children — triage & remediation (Drew acts from the dashboard)

Children — queue visibility & hierarchy

Children — quotas & usage

Children — contracts, performance, access, hygiene

Related programs (distinct epics, don't blur)

Roadmap representation

This issue carries epic + now labels so the orchestrator's label-gated auto-add (#910 rules) picks it into org Project #4 as Kind=Epic; the Area must be pm-dashboard (set by whoever reconciles first pass if auto-add doesn't carry Area — tracked as part of #1143's taxonomy work). Grist "Program roadmap" rows 1-5 cover the ORIGINAL PM phases (complete); a row for this coherence phase is requested in #1144's reconciliation scope rather than written ad hoc.

Done when

All children closed: Drew opens one URL and sees every project, fresh data with honest ages, working triage, a true queue picture, epic rollups, and a health view — and staleness anywhere in the stack announces itself instead of decaying silently.

Acceptance criteria

  • A single URL (mobile or desktop) shows all projects with quotas & usage, page health, and the issues that need Drew's attention — with no silent-zero or fixture-backed state presented as live.
  • Triage is possible from that URL (remediate / respond / basic triage), not read-only, through the same audited action path as the rest of the stack.
  • Queued + in-progress work is legible on the dashboard: what would be picked up next, what is being worked on, what is blocked, and what was done recently.
  • Hierarchy renders with rollups (roadmap item > epic > issue), and the service/port topology (including Kaneo vs the rest) is documented on the dashboard.
  • Every child issue listed in this epic is either closed with evidence or explicitly carried as a named remainder; the epic closes only when Drew's verdict — easy to navigate, coherent, fresh — can be answered yes from the dashboard itself.

Activity

  1. added
    kind/featureNew feature or capability request
    nowOrg Project gate: active priority — orchestrator adds to the board
    epicMeta-issue grouping multiple items (org Project Type=Epic)
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. 113 remaining items

  4. added
    mode/onlineFully doable remotely: design, config, code, cloud
    on Nov 1, 2026
  5. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    Program tending — sub-issue progress (2026-11-02)

    Closed since this thread's last activity: #1277 (closed 2026-11-01T23:31Z), #1284 (closed 2026-11-01T23:48Z), #1279 (closed 2026-11-02T13:06Z).

    Recorded for the parent rollup; this is a progress note, not a completion proposal — the parent stays open on its remaining children.

  6. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  7. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03

  8. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triage verdict: epic still live; its own rollup is stale (hand-maintained checklist 0/35 checked vs 25 children closed)

    Verdict

    Live — keep open. This is a program-tracking epic, not a code item; there is nothing to fix or close here. What triage can contribute is the rollup and the blockers, both of which currently diverge from reality.

    Child rollup (fresh gh reads of all 37 issue numbers in the body): 12 open, 25 closed.

    Defect in the epic itself: the body's "Children" checklist is entirely stale — 0 of 35 boxes are checked while 25 of those children are closed. An epic whose purpose is the hierarchical rollup currently reports the opposite of the truth to anyone reading it, which is the same coherence failure the epic was filed to fix.

    Blockers / ordering

    Recommendation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/lLarge: multi-day or open-ended; expect staged check-insepicMeta-issue grouping multiple items (org Project Type=Epic)kind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmode/onlineFully doable remotely: design, config, code, cloudnowOrg Project gate: active priority — orchestrator adds to the boardpriority/normalOrdinary priority (the default)source/humanFiled directly by a humantask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions