---
digest: >
  v0.18.2 adds manual and assisted journey association tools for conversation
  organization. The Workspace now exposes unassigned conversations, conversation
  detail pages can assign or transfer a conversation to any journey, and the
  unassigned list supports selecting multiple conversations and assigning them
  together. Operations also gains a conservative Conversation journey backfill
  with dry-run, explicit/title-alias modes, approval, backup, progress, and
  evidence. Completed journeys are available in assignment dropdowns.
---

# v0.18.2 — Conversation Journey Assignment

**Date:** 2026-06-02

## Highlights

- Adds an **Unassigned** entry in Workspace for conversations without a journey.
- Adds a Journey selector on conversation detail pages for manual assignment or transfer.
- Adds multi-select bulk assignment from the Unassigned conversations list.
- Includes completed/non-active journeys in assignment dropdowns.
- Adds a conservative **Conversation journey backfill** Operation with preview/apply modes.
- Keeps automated apply protected by approval, backup, and per-conversation progress.

## Where We Started

After the metadata lifecycle release, production data showed that many historical
conversations still had no journey. Automatic repair was too conservative to fix
most of them, and the web UI did not give the user enough control: unassigned
conversations were hard to find, individual conversations could not be moved, and
there was no way to bulk-correct the remaining obvious cases.

## What Changed

Workspace now includes an **Unassigned** surface. It lists conversations whose
`journey` field is missing and lets the user open each one. Conversation detail
pages now include a Journey section with a selector, so a user can assign a
conversation, transfer it to another journey, or mark it unassigned.

For cleanup at scale, the Unassigned surface now supports selecting multiple
conversations and assigning them to a chosen journey in one explicit action. The
journey selector uses all journey identities, not only active journeys, so older
or completed journeys can receive historical conversations.

Operations also includes **Conversation journey backfill**. Its `explicit_only`
mode uses strong activation signals such as `$mm-build mirror-mind`, `/mm:build
ariad`, or explicit jornada/travessia mentions. Its `title_alias` mode adds
unambiguous title aliases. Dry-run is the default; apply requires approval,
creates a backup, and emits assignment progress.

## Production Validation

Production dry-runs found 29 `explicit_only` candidates and 60 `title_alias`
candidates. The manual Unassigned UI and spacing were validated in the local web
server. The completed-journey issue was caught in production use and corrected so
assignment dropdowns include completed journeys.

## Conscious Exclusions

- No LLM-based journey inference is included.
- Ambiguous semantic matches are intentionally excluded from automatic backfill.
- Bulk assignment is selected-only; it does not assign everything visible by default.
- Individual manual journey changes do not require a heavy approval checkpoint, but batch/operation apply remains explicit.

## Next Horizon

If more historical repair is needed, the next step is an assisted review surface
that shows suggested journey, confidence, and evidence with per-row accept/reject
rather than applying ambiguous suggestions automatically.
