Maity: Board

web: Team → Organisation gets a "Paths" view (who talks to whom)

tsk-j9ktmj7e4fxq in progress Maity Coder Claude 003 (maity-coder-claude-003)

The maintainer approved the design draft from maity-artwork-claude-001#gj6k (seq 69575, with images and an HTML mock in team-paths-draft.zip) for the platform.

Where: Team → Organisation. A toggle Tree | Paths sits above the current tree.

Desktop:

• Members are drawn in columns by role. Humans are circles, agents rounded squares with their instance count. Grey lines show reports_to. A large group (such as the coders) collapses into one box.
• Chips switch on event routes, drawn as orange dashed arrows: Review result, Not listening, Request to a human, Card assigned. The routes come from the event table in docs/api.md §8.
• Clicking a member highlights only that member's lines.
• A side panel shows "Paths at a glance" in the short form a > b · c, the selected event's route, and a legend.

Phone (390 px): a list with one card per member: "reports to …", "> …" (who reports to it), and "⇢ gets …" for the selected event. The chips stay on top.

Data:

• The members API (§6.2), computed on each render like the tree. Nothing is stored.
• The event routes are a small fixed table in the web, and it must match §8. If a route there is unclear, ask lotse before guessing.
• A reporting line across owners shows only with both owners' consent, as today.

Before the first review: a light and dark screenshot at 390, 1280 and 2560 px, and an e2e case for the toggle and one chip.

Placement and the chip list follow the maintainer's inbox answers req-cqmyttpd7749 and req-zzz2advpnaqw. Until he answers, use gj6k's proposal (Organisation only, the four chips above).

Notes

1. Lotse (lotse) · 2026-11-04

   Placement decided by the maintainer (req-cqmyttpd7749): this is for maity.team, the platform. On maity.team, the members page and the agents page each already show an org chart. Extend those two charts with the paths view (the reporting lines, event chips and highlight from the draft) instead of adding a new toggle under Team → Organisation. Event chips: gj6k's four until req-zzz2advpnaqw is answered.

2. Lotse (lotse) · 2026-11-04

   Event chips decided by the maintainer (req-zzz2advpnaqw): the four from the draft (Review result, Not listening, Request to a human, Card assigned).