Composition notes

• Question: who is using AI, and is anyone unaccounted for? Two accountings against the identity source's denominator (Okta/Jamf), never the sensor's own sightings: people with no sensor on any device, and covered people who have never run an agent. The inverse — AI use with no person — is Inventory's row; the band names it and links.
• Verdict line is verdicts.teams(world) verbatim at fleet scope; under ?team= the page's own teamsVerdict(world, team) produces the same sentence shape over the team so it cross-foots with the rows on screen.
• Framing band = four claims (Phase1StatBlock): people covered (the one attention device, a filter), devices sensored (deployable vs Windows platform gap, a filter), using AI · 30d (the stalled joiner rides its sub — adoption folds into the claim rather than a lever; the c67 strip stays gated), installs with an owner (a link — one number, one home). All computed from the rows in the table.
• Amber ruling applied: c67 said amber = attribution debt only; the c81 chassis says amber = attention debt only. This page spends its one amber on the coverage gap and states the attribution debt (an install with no identity) in neutral tone with its link. Personal accounts are the red class, in the expand only.
• Team drill-down = filter in place: the strip writes ?team=; verdict, band and roster scope to it. People and measured tokens per team from teamRollup; spend by team is Cost Center's (c67 decision 1).
• Table is the raw UxTableList family so ?id= can pre-open a row through refs. Rows from personRoster(world, team), ranked investigate → uncovered → stalled joiner → tokens; sorters on the rest; search on the Person header. One attention device per row: the Coverage column, except the stalled joiner whose row keeps Coverage quiet and carries amber on Last active = never.
• Expand = the c67 person expand card rebuilt on the world: identity & attribution (team chip filters in place, devices and accounts as Phase1EntityChips with sensor/licensing subs, "user detail →"), attention (derived items, each with a verb-link; absent when clean), agents & usage (one row per install with monitored pill, licensing badge, 7d sessions and tokens, "view details →"; then the 30d usage line with models, repos, MCP servers). Sessions stay on User detail — the card prints the count.
• Derivation: every number traces to coverageStats / teamRollup / stalledJoiners / monitoredStats through derived/teams.ts. The Okta/Jamf integration state is a world fact (world.integrations, folded in at reconcile) — the denominator line reads it, the page asserts nothing.
• Open: whether the stalled joiner deserves its own band claim; "partial" vs "1 of 2" as the coverage word for a Windows-gap person; the page name (Linear's "Teams & Users" kept; c21 floated "Users / Devices").