Human Resources > Manager -- Rooster's live view of staffing, people exceptions and management work (HR_HANDOFF/README.md §4, Track E).

⛔THE COMPOSITION ROOT FOR THE MANAGER READ MODEL, AND THE ONLY PLACE THAT KNOWS BOTH HALVES. workforce.manager_view is read-only domain and deliberately does not import floor_blocks; the have-of-need instrument it needs for Staffing health is the SAME payload the Schedule tab reads, built here and handed in, so there is no second coverage computation.

⛔AND IT IS THE ONLY DEFINITION OF THIS PATH. Two builds arrived at GET /api/floor/hr/manager independently and for a while both were registered; FastAPI answers with whichever was imported first, so the second was a route nothing could reach and no gate reads a duplicate path as an error. The two read models are BOTH kept and BOTH reached from here, because they answer different questions:

• workforce.manager_view.board is the BOARD -- open management work, people needing attention, staffing health, coaching, requests, per-work activity, and the policy register.
• rooster.executive.manager_timeline.manager_payload is the management COMMUNICATIONS timeline -- one UNION over cover_asks, cover_responses, announcement_recipients, escalations and employee_requests, ordered by the clock and limited ONCE, with one sentence per event composed API-side. ⛔Six reads each limited to N and merged afterwards is a window with holes in it that read as quiet periods, which is why it stays one statement and is not folded into the board's per-work events.

⛔A RECORDING IS NAMED AND NEVER RETURNED. Timeline events carry detail_kind/detail_ref; fetching the thing they name is a separate, separately permissioned read that this route does not perform.

⛔GATED hr:schedule:read, THE SAME GRANT /hr/schedule ALREADY HOLDS. Manager is the section's landing page and Staffing & Schedule is one of its tabs; a second grant for the same data would be a permission that exists only because a screen was renamed.

⛔AND THAT IS A NARROWING FOR ONE POPULATION, SAID OUT LOUD RATHER THAN DISCOVERED. The timeline half used to be gated hr:contractors:read. Folding it in under the board's grant means a principal holding ONLY hr:contractors:read no longer reads this route: the HR section still unlocks for them (web/src/lib/access.ts SECTION_FUNCTION_KEYS.hr accepts either key) and Contractors and Onboarding still open, but the section's landing page refuses them at its ProbeGate. That follows from HR_HANDOFF/README.md §1 making Manager the section's entry point on the schedule grant, and it is Frederick's sitemap decision rather than one taken here -- recorded so nobody has to rediscover it from a 403.

⛔NO WRITE LIVES HERE AND NONE MAY. README §11: every decision is a card on Frederick's Today. An escalated item carries one link and no control.