Back to the changelog

• Feature

  Process Map: Time and Cost lenses

  The Activity toggle becomes a selector — Design | Activity | Time | Cost — with a 7/30/90-day period. One lens at a time paints the map with a relative heatmap (the worst node glows the most, neutral→amber: red stays reserved for alerts). The Time lens shows real lead time vs the expected time (declared SLA → sum of state timeouts → historical median) with an explicit deviation; the Cost lens shows period and per-item cost with the human/automation/AI split and a hint on tasks without a configured cost.

• Feature

  Operational alerts on the map

  Derived alerts, zero configuration: a node pulses red with items awaiting WIP, past timeout, past SLA or in statistical stall (stuck beyond 3× the historical median of that phase). Wired-but-silent edges get the dormant badge. The map Diagnostics gains a live Operational alerts section — click to zoom on the node; auto-refresh every ~45 seconds in cockpit mode.

• Feature

  Declared flow SLA

  New Item SLA (minutes) field in the flow settings (literal or variable expression): the maximum expected time to complete an item. Advisory only — breaches raise an alert on the map, no automatic action. The SLA is preserved across new versions, export/import and templates.

• Feature

  Drill-down: from map to item in two clicks

  Click a flow node in cockpit mode → Operations section in the inspector: the 5 oldest active items (age and assignee), click → quick view without leaving the page (transitions included), and from there the full item page. Plus a trend sparkline (weekly median lead and cost) and "See all in Monitor" opening the item list already filtered on the flow, in a new tab.

• Design

  Actor view and animated traffic

  Click an Actor node in cockpit mode → the map isolates its reach (connected flows, both directions) with a summary badge: "Purchasing: 12 active items, 2 alerting". Esc to exit. Edges with real traffic show animated dots flowing along the path, density proportional to volume — you can see where the process pulses. Respects the system reduced-motion preference.

• Integration

  Flow Agent and MCP: the cockpit you can ask

  The Flow Agent knows your Process Maps: ask "how is the orders process doing?" — it lists the maps, reads activity, time vs expected, costs and alerts, and gives concrete advice (bottlenecks, tasks without cost, missing SLAs, dormant edges). Same data exposed as MCP tools (list_process_maps, get_process_map_health) for agentic integrations: aggregates only — never item data — and fail-closed denial for flow-scoped keys.