---
digest: >
  v0.20.0 introduces one-level hierarchical journey organization. Journeys can
  now name a parent journey, the web console can create and edit that parent
  relationship, and Workspace renders the hierarchy with session-persistent
  expand/collapse. Journey settings also gain safe title and status editing, and
  textual journey lists preserve the same hierarchy through mm-journeys. The
  release keeps hierarchy display-only: conversations, memories, tasks, routing,
  Builder context, extraction, and search remain journey-specific.
---

# v0.20.0 — Hierarchical Journey Organization

**Date:** 2026-06-02

## Highlights

- Adds `parent_journey` metadata for one-level journey hierarchy.
- Adds parent selection to **New journey** and Journey Settings in the web console.
- Adds safe Journey Settings editing for title and status without changing the slug.
- Renders parent/child journeys in the Workspace sidebar with session-persistent expand/collapse.
- Keeps completed journeys hidden by default behind a toggle while preserving hierarchy when shown.
- Dims paused and completed journeys so active journeys remain visually primary.
- Updates `mm-journeys` / `python -m memory journeys` to render the hierarchy and preserve indentation.
- Updates journey-list skill instructions so natural-language journey-list requests preserve the hierarchical output.

## Where We Started

The web console had become useful enough for conversation and journey
maintenance that a flat journey list started to become the next source of
friction. Some journeys clearly belonged under broader fields of work, but the
product had no way to express that relationship. At the same time, completed
journeys still needed to be accessible for editing and reassignment without
polluting the active sidebar all the time.

The exploration behind CV15 sharpened the boundary: hierarchy should organize
attention, not merge identity. A child journey remains a normal journey with its
own conversations, memories, tasks, Builder context, routing, and extraction.
The parent journey is a visible broader field, not an implicit context mix.

## What Changed

Journey metadata now accepts a `parent_journey` field with guarded validation.
A journey can have one parent, the parent must exist, a journey cannot parent
itself, and the first slice rejects deeper nesting. The web console exposes this
through **New journey** and Journey Settings.

Journey Settings also gained safe title and status editing. The title edit
updates only the first markdown H1 in the journey identity. The status edit
updates only the `**Status:**` line. Neither operation renames the slug or moves
conversations, memories, tasks, attachments, routing descriptors, or Builder
configuration.

Workspace now renders the journey sidebar hierarchically. Parent journeys can be
expanded or collapsed, and that expansion state persists for the browser session.
Paused and completed journeys are visually dimmed. Completed journeys are hidden
by default behind a toggle, but when shown they appear in their correct
hierarchical position rather than in a separate flat archive list.

The textual journey list now uses the same hierarchy. `/mm-journeys`,
`/mm:journeys`, and natural-language journey-list requests route to the CLI
rendering and preserve its indentation instead of flattening it.

## Conscious Exclusions

- No Scene Workspace Home is included in this release.
- No LLM synthesis is included in this release.
- No automatic parent-child memory, routing, Builder, extraction, task, or search inheritance is introduced.
- No recursive hierarchy or multiple parents are supported.
- No journey slug rename or deletion cascade is included.

## What We Learned

A hierarchy can easily become a folder system if the product treats it as only a
navigation convenience. The useful boundary is more precise: hierarchy organizes
the field so the Mirror can later return cognitive location. This release
therefore keeps the implementation deliberately structural and display-only,
preparing the ground for Scene without pretending Scene already exists.

## Next Horizon

The next release in CV15 is **Scene Workspace Home**. With the hierarchy now
available as a stable read model, Workspace can begin answering “where am I
now?” through a Scene surface, movement signals, horizons, and bounded LLM
synthesis over existing Mirror data.
