Dynamic cards
Dynamic cards are the family of result-surface primitives that compose into chat responses, board-meeting receipts, equity-event summaries, and any AI-output surface. They live under the CK namespace in @matter/components.
Phase tones — the three frames
plan
Plan
Resolving jurisdiction defaults and proposing a formation packet.
execute
Execute
Filing charter with DE Secretary of State…
respond
Respond
Entity `ent_a7f3` registered. Certificate attached.
Six sub-pages cover the primitives:
- Frame & flow —
CK.Frameouter shell with phase tone (plan / execute / respond) and motion grammar. - Data display —
CK.Value,CK.Money,CK.Delta— typed value readouts. - Process & metrics — step receipts, progress, run summaries.
- People & parties — attribution primitives (signer rows, attendance, agent badges).
- Domain artifacts — typed legal artifacts (cap-table rows, filing receipts, plan summaries).
- Editor primitives — inline editor inside the card footer.
Why a separate family
Static cards (see Cards) are opaque content surfaces. Dynamic cards carry state — the model emitted them, they may stream in, they expose action affordances. The frame's phase tone (plan / execute / respond) signals where the work is.