Topics are where Runwita stops being a meeting note app and starts being something else. A topic is a recurring thread, a thing that comes up in multiple conversations, that you want to track over time. “Licensing model”, “Migration timeline”, “Onboarding flow redesign”. Each topic has a state (open, blocked, decided, resolved), a category, and a chronological log of touchpoints across engagements.Documentation Index
Fetch the complete documentation index at: https://docs.runwita.com/llms.txt
Use this file to discover all available pages before exploring further.
Why topics exist
In meeting note apps, every meeting is a flat island. You search for “licensing” and you get five separate transcripts, each with their own context, and you have to mentally stitch the arc back together. The thread isn’t first-class. In Runwita, the thread is the object. The engagements are how the thread accumulates new state. When you scroll a topic, you see:- The most recent state (e.g. Decided).
- Every prior touchpoint, in order, with the engagement it came from and what was said about the topic in that meeting.
- A category (technical, commercial, governance, planning, relationship).
- A status timeline, when it became blocked, when it unblocked, when it was decided.
How topics get created
You don’t create topics manually. They’re created by the AI during the topic-matching step that runs when you save an engagement. For each section in your extracted engagement, the AI looks at:- The section’s heading and body.
- The journey’s existing topics (their titles, statuses, categories).
- Substance, not section title. “License discussion” and “SAC Licensing Renewal” are the same topic, not two. The matcher looks at content overlap.
- No fragmenting. A topic only appears once per engagement, even if multiple sections discussed it. The matcher merges them into one touchpoint.
- Logistics aren’t topics. Greetings, scheduling next meetings, off-topic chitchat don’t get topics. Only substantive recurring threads do.
- 2 to 6 topics per meeting. That’s the matcher’s target band. Not every section needs its own topic.
Topic state
Each topic has a status that reflects where it stands. The status updates whenever a new touchpoint lands.| State | What it means |
|---|---|
| Open | Active discussion, no terminal decision. The default state for any new topic and any topic that’s currently moving forward. |
| Blocked | An impediment was raised and not yet resolved. “We can’t proceed until legal signs off.” |
| Resolved | The topic is complete, no more discussion expected. Terminal. |
| Stale | No touchpoint in a long time (configurable per topic). Auto-flagged so the journey doesn’t quietly leak attention. |
| Touchpoint state | Maps to topic state |
|---|---|
discussed | open |
progressed | open |
decided | open (the topic continues; the decision is recorded as a Decision on the engagement) |
blocked | blocked |
resolved | resolved |
Categories
Each topic has a category, used for filtering and visual grouping on the journey page. Five categories:- Technical — architecture, integration, infrastructure, data.
- Commercial — pricing, licensing, contracts, terms.
- Governance — compliance, security, privacy, audit.
- Planning — timelines, milestones, scope, capacity.
- Relationship — stakeholder dynamics, communication patterns, escalations.
Reading the topic timeline
Click any topic on a journey page to see its touchpoint history. Each row is one engagement that touched the topic, with:- The date of that engagement.
- The state at that touchpoint.
- A brief note (one to two sentences from the AI summarising what was said about this topic in that meeting).
Editing topics
Topics are editable. From a topic’s detail page you can:- Rename the topic.
- Change its category.
- Manually flip its status (e.g. mark something resolved before the next meeting confirms it).
- Edit individual touchpoint notes.
- Delete the topic (which removes all its touchpoints; the underlying engagements stay intact).
When topics go wrong
Topic matching is imperfect. The two failure modes you’ll see: Over-fragmentation. The matcher creates a new topic when it should have continued an existing one. Usually because the engagement section was worded differently from the existing topic’s title. Fix: open both topics, edit one to match, and either re-run extraction (Reprocess with AI) or manually move touchpoints. Over-merging. The matcher attaches a section to the wrong existing topic because the surface words overlap but the substance is different. Less common but harder to spot, you usually catch it weeks later. Fix: split the touchpoint off into a new topic from the topic detail page. If you find the matcher is consistently off on a journey, two levers help:- Use a sharper, more capable model on the workhorse tier. Claude Haiku 4.5 and gpt-5 do better than gpt-5-nano on this task.
- Give your topics more distinctive titles. “Licensing” matches everything; “SAC licensing renewal terms” matches only its actual thread.
What’s next
AI tiers
Frontier and Workhorse, and which one runs topic matching.