> ## 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. # Journeys > The thread that holds everything else together. A journey is the single longest-lived object in Runwita. Everything else, engagements, topics, decisions, actions, people, attaches to a journey. If the journey is the spine, the rest is the body that hangs from it. ## What a journey is, in practice A journey is a customer + a use case. That pair is the identity. It's deliberately not just a customer name, because one customer can have several parallel things going on with you. Examples: | Customer | Use case | What it groups | | -------------------- | --------------------------- | -------------------------------------------------------------------- | | Maplewood Inn | Digital ordering rollout | Discovery calls, design reviews, weekly check-ins, go-live planning. | | Acme Corp | Q4 renewal | Renewal reviews, pricing negotiations, redlines, signature. | | Year 11 Lit students | Semester two reading scheme | Lesson plans, parent updates, progress checkpoints, exam prep. | | Internal | Q3 hiring plan | 1:1s with hiring managers, interview debriefs, calibration sessions. | | You | Personal | Your own quarterly planning, retros, journal-style entries. | A journey doesn't have a fixed end. It runs as long as the relationship or initiative is active. Some last a quarter, some last for years. ## What a journey gives you Once a journey has even three or four engagements on it, the value compounds: **Threaded history.** Every engagement that touches the journey shows up in chronological order, with summaries, decisions, and actions inline. Scroll the journey page and you read the story of the relationship. **Topic tracking.** Recurring threads of discussion get their own object. If *"licensing model"* comes up across four engagements with three different states (discussed, blocked, decided, decided again), you see the arc, not just the last entry. See [Topics](/concepts/topics) for the deeper logic. **Decisions and actions, deduplicated.** Open actions across all engagements roll up to a single list per journey, so you're not hunting through individual ones. Decisions stack chronologically. **People.** Stakeholders on the journey, pulled from attendees, with their role and the engagements they've been in. A relationship map per journey. **Intelligence.** Once enough engagements are stacked up, Runwita can run higher-level analyses: deal health, sentiment, stale-flagging, executive summaries. These are explicit features you trigger, not background magic. See [Intelligence](/concepts/intelligence). ## How journeys work with the AI matcher When you save an extracted engagement, Runwita asks the AI which journey it should land on. The matcher sees: * The engagement title, summary, and detected customer. * Your full list of journeys (customer + use case + summary). It returns one of: high-confidence match, medium-confidence match, low-confidence (needs your pick), or no match (suggests creating a new journey). The matcher works much better when your journey use cases are specific. *"Licensing renewal"* is far more matchable than *"Engagement"* or *"Working sessions"*. If you're getting frequent "no match" results, look at the use cases of your existing journeys, that's usually where the signal is too thin. ## When NOT to use a journey A journey is the wrong abstraction when: * The conversation won't recur. A one-off interview, a single phone call with someone you'll never speak to again, a panel you sat on. These can still be saved (Runwita will create a journey for them if you ask) but the value compounds on threads that recur. Standalone events sit lonely. * The "thread" isn't really one thread. If you find yourself with a journey called *"Acme Corp, all things"*, you'll hit a wall. Multiple parallel use cases for the same customer are easier to track as multiple journeys. The matcher gets sharper, the topic graph stays clean. * The engagement is private journaling. Runwita supports it, but a personal journal works just as well in a markdown file. The cost of a journey starts to outweigh the benefit when you're the only stakeholder and there's no recurring decision graph. ## Renaming, archiving, deleting You can rename a journey at any time, customer and use case fields are editable on the journey page. Existing engagements re-anchor automatically. Archiving (hiding a journey from the active list) is on the roadmap but not shipped yet. Deleting a journey removes it and **everything attached**: engagements, topics, decisions, actions, attachments, all of it. There's a confirmation step. The deletion is transactional, either everything goes or nothing does. ## What's next A single conversation, captured. Threads that span engagements.