agent-team dashboard: refine pipeline map visuals #71

New issue

Closed

opened 2026-06-25 16:22:38 +00:00 by amoussa1229 · 1 comment

amoussa1229 commented

2026-06-25 16:22:38 +00:00

(Migrated from github.com)

Summary

The pipeline map (PipelineMap + dagre auto-layout in agent-team/web/src/layout.ts, node meta in agent_team/topology.py) renders correctly but has some visual rough edges worth polishing — surfaced while adding the Confluence-writer 'docs' lane on PR #66.

Concrete items

Multi-entry lanes render as backward loop-backs. conf_draft is reachable from BOTH intake (Flow A) and verify_node (Flow B). Because it ranks early (reachable from intake), the Flow B edge verify_node -> conf_draft classifies as a loopback and draws as a backward arc, which reads like a retry rather than a forward 'document this change' branch. Consider a distinct edge style/semantics for cross-lane forward branches vs true retry loops.
Branch vs spine emphasis. With the docs lane, intake is now a conditional branch point (intake -> clarify is a branch, not spine), so the primary flow loses its solid-spine emphasis. Consider styling the dominant/default path as the spine even when the source is conditional.
Process-tree grouping. Trees (core / sdlc / docs) are data-only today; the map doesn't visually group or color by tree (swimlanes/background tint/legend). Consider visible lane grouping so the SDLC vs Documentation processes read at a glance.
Gated/opt-in affordance. gated nodes are dimmed; revisit whether dimming still reads well now that gated lanes (P3, Confluence) can be live (see the 'gated != inactive' nuance).

Pointers

agent-team/web/src/layout.ts (dagre layout, edge styling, loop-back labels)
agent-team/web/src/components/PipelineMap.tsx, MapNode.tsx
agent_team/topology.py (_edge_kind spine/branch/loopback classification, TREES, NODE_META)

Context: follow-up from the Confluence-writer dashboard work on PR #66.

## Summary The pipeline map (`PipelineMap` + dagre auto-layout in `agent-team/web/src/layout.ts`, node meta in `agent_team/topology.py`) renders correctly but has some visual rough edges worth polishing — surfaced while adding the Confluence-writer 'docs' lane on PR #66. ## Concrete items 1. **Multi-entry lanes render as backward loop-backs.** `conf_draft` is reachable from BOTH `intake` (Flow A) and `verify_node` (Flow B). Because it ranks early (reachable from intake), the Flow B edge `verify_node -> conf_draft` classifies as a `loopback` and draws as a backward arc, which reads like a retry rather than a forward 'document this change' branch. Consider a distinct edge style/semantics for cross-lane forward branches vs true retry loops. 2. **Branch vs spine emphasis.** With the docs lane, `intake` is now a conditional branch point (`intake -> clarify` is a `branch`, not `spine`), so the primary flow loses its solid-spine emphasis. Consider styling the dominant/default path as the spine even when the source is conditional. 3. **Process-tree grouping.** Trees (`core` / `sdlc` / `docs`) are data-only today; the map doesn't visually group or color by tree (swimlanes/background tint/legend). Consider visible lane grouping so the SDLC vs Documentation processes read at a glance. 4. **Gated/opt-in affordance.** `gated` nodes are dimmed; revisit whether dimming still reads well now that gated lanes (P3, Confluence) can be live (see the 'gated != inactive' nuance). ## Pointers - `agent-team/web/src/layout.ts` (dagre layout, edge styling, loop-back labels) - `agent-team/web/src/components/PipelineMap.tsx`, `MapNode.tsx` - `agent_team/topology.py` (`_edge_kind` spine/branch/loopback classification, `TREES`, `NODE_META`) Context: follow-up from the Confluence-writer dashboard work on PR #66.

amoussa1229 commented

2026-07-14 23:03:14 +00:00

(Migrated from github.com)

agent-team subsystem was decommissioned 2026-06-26 and this repo is being archived — closing as not planned.

This repo is archived. You cannot comment on issues.