ShrubberyDocs
Sign in

Garden Overview

Overview

The Garden is the Lead's home screen at /dashboard. It surfaces every Shrubbery the Lead owns (assigner = current user), grouped by status, with the Lead's own Commitment Flow Score widget at the top. The Garden is read-only — all state-changing actions happen one click deeper, inside the Detail Sheet.

Actors

  • Lead — the only persona that consumes the Garden. The route is the Lead's daily orientation surface.
  • Knight — does not see the Garden directly. The role-toggle on the same route lets a user viewing their own dashboard switch perspective; this is a UI affordance, not a separate route.

Flow

  1. Lead opens /dashboard — the page renders three live columns: Draft, Pending_Handshake, Active. Terminal states (Completed, Refused) collapse into an archive section.
  2. Lead scans the CFS widget — Flow Score (Say-Do Ratio), Ghost Rate (Refused + aged-out), and Reciprocity (Lead's own Say-Do as Assignee). Numbers update live as Knights handshake and complete.
  3. Lead clicks a card — the Detail Sheet opens as a 480px side-sheet without leaving the route.
  4. Lead performs an action in the Detail Sheet (send to Knight, edit, mark complete, etc.) — the Garden column updates in place as the state transitions; the side-sheet stays open.

Edge cases

  • Knight role toggle — ?role=knight filters the same query to rows where assignee = current_user. The CFS widget recalculates against the Knight-as-assignee subset. A ?role=all view shows both, useful when a user wears both hats.
  • Renegotiated Shrubberies — return to the Pending_Handshake column with a visual indicator marking that they were previously Active. The card itself does not duplicate.
  • Empty state on first login — the Garden shows the Capture entrypoint (Smart Paste / URL Drop / Manual Contract) front-and-centre rather than empty columns.
  • Stale Pending_Handshake — receives a Nudge email/Teams DM via the Inngest cron; the card stays in column, but the Nudge timestamp surfaces on hover.
  • Archive performance — terminal-state rows are collapsed and paginated; the page does not render thousands of historical cards eagerly.

Last updated: 17 May 2026