Dataflow Detail

The app needs a focused view for individual dataflow detail pages — exactly two actors (source → destination) connected by a single flow line, sitting at the top of a "Dataflow" detail page. Unlike the full map, this view lets users toggle context per actor: revealing boundary rugs (Security Zone, Team, Region) that show where each actor sits in the broader system, without the noise of the full network map.

Build a view state for showing a single dataflow with larger actors, and allow toggling contexts independently for the source and the destination actor.

• 2026-03-23 — Landed in the qmap c14+ release commit alongside the broader visualization engine:
  • New QMapDataflow wrapper component promoted to src/components/ and exported from the library
  • Per-actor context toggling via sourceContexts / destinationContexts props; dynamic visibleActors (focal actors + context siblings sharing tag values) and groupBy computed from active context keys
  • Reused useHighlightedDataflows for focal actor scaling and non-focal dimming
  • Experiment harness at dev/experiments/c17.dataflow-detail/ with a focal-dataflow picker and per-actor context toggle buttons; test data of 10 actors across 3 security zones and 3 teams, 10 dataflows, 5 curated focal selections

Initial scaffold worked: the QMapDataflow wrapper shipped in the library and the experiment demonstrated per-actor context toggling over curated focal dataflows. Visual tuning and camera framing for 2-actor scenes were left open. c19 rebuilt this wrapper on the c18 config schema system (config-driven props, DATAFLOW_DEFAULTS), which replaced the hardcoded props from this cycle.