Roster

A Roster is a team roster — people with a name, role, tags, and an optional reportsTo that draws the reporting lines. Humans read cards grouped by who-reports-to-whom; the agent gets { kind:"roster", people:[{ id, name, role, reportsTo }] } — each person addressable as entity:person/${slug}, the org tree expressed as reportsTo edges between ids. So "who reports to X?" or "everyone tagged agent" is a query, not prose-reading.

When to use it

Team pages, org charts, contributor lists, on-call rosters. The reporting lines render as an indented structure and serialize as resolved reportsTo ids, so the org graph is queryable.

Props

Roster

RosterPersonInput

What the agent sees

Each person gets a stable id, and reportsTo is resolved from a name/slug to that manager's id — so the org structure is a real edge an agent can traverse:

{
  "kind": "roster",
  "id": "core-team",
  "title": "Core team",
  "people": [
    {
      "id": "krishnan",
      "name": "Krishnan S G",
      "role": "Head of Engineering",
      "slug": "krishnan",
      "tags": ["lead"]
    },
    {
      "id": "scaffolder",
      "name": "Agent: Scaffolder",
      "role": "Scaffold skill",
      "slug": "scaffolder",
      "reportsTo": "krishnan",
      "tags": ["agent"]
    },
    {
      "id": "author",
      "name": "Agent: Author",
      "role": "Vibe skill",
      "slug": "author",
      "reportsTo": "krishnan",
      "tags": ["agent"],
      "refs": [{ "rel": "related", "target": "/docs/skills", "label": "Skills", "internal": true }]
    }
  ]
}