Components Inventory
actors
Inventory Ledger Structure
Roster of responsibilities owned by named actors.
Use to show 'who owns what' across a process, scoring policy, or org chart. Two-column layout: actor on left, responsibilities on right.
When to use
- Who owns what. Each row pairs a named actor with the slice of work they own. Use when the audience needs to know accountability, not process flow.
- Three to six actors. The ledger reads cleanly up to about six rows. Past that, split the roster across two slides or roll up adjacent roles.
- One-line responsibilities. Each actor's body is a short responsibility summary, not a job description. Detail belongs on a follow-up slide or in an appendix.
When not to use
- Process sequence. If the rows describe stages in order, use list-steps or process-flow. actors is for parallel ownership, not handoff sequence.
- Long per-actor prose. More than one sentence per row crowds the ledger. Move the detail to a dedicated slide and keep actors as the index.
- Roles without names. If the labels are job titles in the abstract ("the engineer"), reach for cards-stack or list. The actors layout earns its weight when the names are named.
Slots
| Slot | Selector | Required | Description |
|---|---|---|---|
title | h2 | yes | Slide heading. |
rows | ul > li | yes | One row per responsibility. Each li leads with the responsibility label — rendered bold automatically (no … needed) — then a trailing inline-code actor name (rendered as a right-aligned categorical pill), then an optional nested bullet carrying a one-line body. |
Anatomy
┌─────────────────────────────────────────┐
│ header │
│ Actors heading. │
│ │
│ Role A Owner name │
│ - responsibility one │
│ Role B Owner name │
│ - responsibility two │
│ │
│ footer 1/19 │
└─────────────────────────────────────────┘