premise

StatementSplitSeries

A framing claim beside a vertically centered ledger of parallel rows — a number, a term, a description, and a right-aligned note, each row colored by its own categorical hue.

Open in Playground

Use when a deck needs to introduce an ORDERED vocabulary — a maturity ladder, a set of named stages, a ranked taxonomy — and wants one framing claim to sit beside the whole list at a glance, not one slide per term. The claim doesn't summarize the rows; it states why the ordering matters. Each row is a fixed four-part record: an index, the term, one description clause, and a short framing question or note, right-aligned. Both zones share the page's own background — unlike split-panel, there's no colored panel divide.

onboardingrankingdefinitionoverview

When to use

An ordered vocabulary needs one overview slide. A maturity ladder, a named set of stages, a ranked taxonomy — anything with 3-8 ordered terms that deserves a single at-a-glance slide before the deck dives into each one individually.
The claim explains the ORDER, not the list. The heading + lede earn their place by saying why the ranking matters ("growth is a change in thinking, not title") — if there's nothing to claim about the ordering, a plain list serves better.
Every row shares the exact same four-part shape. Index, term, one clause, one right-aligned note. A row that needs more than that (a nested sub-list, a multi-sentence description) has outgrown premise — reach for cards-stack or a per-term split-panel proof slide instead.

When not to use

Rows with unequal structure. Every row must carry all four segments in the same order. A row missing its trailing note, or with a two-clause description, breaks the ledger's scan rhythm — trim or pad it to match its siblings.
More than eight rows. The categorical palette cycles at eight; past that, split into two premise slides by group rather than repeating hues.
The heading summarizes the rows instead of claiming something. "Six cognitive verbs" restates the list; "growth is a change in thinking, not title" claims why the list matters. If the heading can't be argued with, it's a caption, not a premise.

Common mistakes

Writing the row as a nested - Title / - body pair instead of one inline line. premise rows are ONE line with four inline segments (code, bold, plain text, italic) — the nested title+body pattern other card-style layouts use doesn't apply here; the row parser looks for a <strong>…</strong> immediately followed by descriptive text and a trailing <em>.
Omitting the trailing italic note, expecting the row to still align. The note's column is reserved whether or not it's authored — an empty note leaves a blank cell rather than collapsing the row, so pad it or the row reads unfinished.

Authoring

<!-- _class: premise -->

## The claim the ledger exists to support.

One or two sentences naming the axes the rows below walk.

1. First term
   - A short clause describing it.
   - A question it answers?
2. Second term
   - A short clause describing it.
   - A question it answers?
3. Third term
   - A short clause describing it.
   - A question it answers?

Slots

Slot	Selector	Required	Description
`heading`	`h2`	yes	The claim — why the ordering in the ledger matters, not a summary of it.
`lede`	`h2 + p`	yes	One-to-two sentence framing paragraph under the claim, naming the two axes or dimensions the ledger's rows walk.
`rows`	`ol > li`	yes	Each row is a NUMBERED item: the term on the item's own line, then exactly two nested bullets — the description clause, then a short framing question. The ordinal is a CSS counter (never author-typed, so rows renumber on reorder) and the term bolds automatically. 3-8 rows; each is colored by its own slot in the theme's categorical palette.

Data shape

Rows should be authored in the ranking's natural order (lowest to highest, or first to last) — the row order IS the categorical color order.
Up to eight rows are colored from the categorical palette before hues repeat; past eight, split into two slides.

Anatomy

┌─────────────────────────────────────────┐
│  The claim,      01 Term  clause  note  │
│  why the         02 Term  clause  note  │
│  order matters.  03 Term  clause  note  │
│                  04 Term  clause  note  │
│                  05 Term  clause  note  │
│                  06 Term  clause  note  │
└─────────────────────────────────────────┘

split-panelthe featured element deserves its own colored panel, not a shared background
list-tabularthe rows need MORE than four fields, or a header row naming the columns
cards-stackeach term needs its own multi-sentence body, not a one-clause row
glossarythe terms are unordered and there's no claim to make about their sequence