Skip to content
Kira LOCAL-FIRST
Editorial cards

Cards are curated context for Kira, not agenda topics.

Use cards to store a take, hook, counterpoint, or research angle that Kira may inject when a matching agenda topic or direct host question appears.

Plain-language version

A card is a sticky note for Kira. It tells her: "if this topic comes up, remember this prepared point." It is not the whole stream plan.

Card lifecycle

1

Draft

Write the idea while it is still hidden from Kira.

2

Arm

Mark it ready so Kira can use it when the right moment appears.

3

Match or link

Attach automatically by triggers, or link it deliberately to a topic.

4

Use or rearm

Keep history, disable stale notes, or rearm useful knowledge.

Quick path

  1. 1 Create a card with topic, summary, streamer take, optional counterpoints, hooks, triggers, and expiry.
  2. 2 Arm the card when it is ready. DRAFT cards are invisible to Kira.
  3. 3 Let auto-attach match an ARMED card to an agenda topic, or use link for a deterministic override.
  4. 4 Use rearm for reusable knowledge, disable for stale cards, and delete only when you really want hard removal.

Lifecycle

DRAFT

Editable and invisible to Kira. Safe staging state for humans and agents.

ARMED

Eligible for auto-attach, direct host injection, or explicit link.

ACTIVE / USED

ACTIVE means selected for a topic; USED preserves history after Kira consumes it.

EXPIRED

Excluded from matching. Can be rearmed when the content becomes useful again.

What users should write

Write the point

Keep the card focused: one take, one hook, one useful detail, or one counterpoint.

Add trigger words

Add names, games, topics, and phrases a host may actually say live.

Do not dump research

Summarize first. Kira needs a clean live cue, not a wall of notes.

Rules that matter

Cards vs topics
Cards are reusable knowledge. Topics are agenda instances. Do not use cards as a replacement for the topic queue.
Triggers are important
Conversational host input may not overlap the card title. Add triggers such as game names, people, or recurring phrases.
Chat never triggers card injection
Only the direct host path qualifies. Chat and SmartAggregator snapshots must not silently inject cards.
Link must match topic slug
The CLI validates topic_id against the card topic slug before activating a deterministic link.