---
digest: >
  v0.23.0 completes the first durable Explorer Mode release. Explorer now holds
  an Exploratory Story beyond one fragile runtime session, resumes it visibly,
  thickens it through required surfaces, and can promote it into Builder with
  provenance-rich handoff evidence. The release also hardens the Explorer/Builder
  boundary: required Explorer cards are marked for runtime rendering, operational
  mutation requests route through Builder, and Pi status-line mode state is
  scoped to the active session. Multiple simultaneous stories and the future Soul
  Mode implementation remain outside this release.
---

# v0.23.0 — Durable Explorer Mode

**Date:** 2026-06-07

## Highlights

- Adds durable `exploratory_stories` storage with active, archived, and promoted lifecycle states.
- Resumes active Exploratory Stories when Explorer Mode is activated for a journey.
- Links Builder handoff artifacts to durable story ids and source conversation evidence.
- Adds privacy-safe optional `full-conversation.md` export with obfuscation for sensitive evidence.
- Marks required Explorer surfaces so Pi can render user-facing cards before commentary.
- Routes clear operational mutation requests from Explorer to Builder before file, code, or doc changes.
- Makes Pi operating-mode status session-scoped to avoid footer leaks between simultaneous sessions.

## Where We Started

Explorer Mode had already proven the conversational shape of exploration: a user
could enter the lens, open an Exploratory Story, thicken it, name attractors,
propose experiments, and promote a candidate into Builder. The weakness was that
Explorer still depended too much on a fragile session and on assistant discipline.
A real Soul Mode validation exposed the gap: the handoff captured final state,
but not enough of the source conversations, thickening path, examples, decisions,
and uncertainty that made the exploration trustworthy.

The release therefore needed to turn Explorer from a promising mode into a
recoverable, inspectable product surface.

## What Changed

Explorer Stories are now durable records. The new storage layer keeps one active
story per journey, preserves historical archived and promoted stories, and stores
the evolving story fields: title, current story, narrative summary, last card,
attractors, experiment proposal, Builder handoff state, and source conversation
metadata. Activating Explorer Mode for a journey now resumes the active story
with `△ EXPLORATORY STORY RESUMED` instead of silently starting from an empty
field.

Builder handoff became an editorial transfer artifact. Handoff generation can
attach source conversations, preserve their role in the exploration, list source
evidence in `index.md`, and write a `handoff-info.md` completeness checklist. Raw
conversation evidence is intentionally opt-in through `--include-full-conversation`.
When included, Mirror writes privacy-reviewed material and obfuscates local paths,
secrets, emails, and phone-like values before creating `full-conversation.md`.

The runtime boundary also became stricter. Explorer command output can wrap
required user-facing cards with stable `[[MIRROR_REQUIRED_SURFACE_BEGIN:...]]`
and `[[MIRROR_REQUIRED_SURFACE_END:...]]` markers so the assistant runtime knows
which surface must be rendered first. The Pi Explorer skill now instructs the
assistant to show the required block while hiding marker lines. It also names the
operational boundary explicitly: Explorer preserves uncertainty; Builder executes
commitment. If the user asks Explorer to edit files, apply procedures, create
code, run commands, or otherwise mutate project state, Mirror should answer with
`△ EXPLORER → BUILDER BOUNDARY` and route the work into Builder before mutation.

A validation bug in Pi's footer was fixed at the same boundary. Operating mode
state used to be effectively global, so two open Pi sessions could overwrite one
another's status line. Mode activation, deactivation, lookup, Builder load,
Explorer load, and `welcome --status-line` now accept a session id. The Pi
extension passes the current session id, while CLI callers without a session id
retain a global fallback.

Finally, stale Explorer copy was removed. Explorer no longer describes itself as
an experimental mode whose full experience will be available soon. The activation
surface now states that Explorer Mode is active and ready for durable exploration,
story thickening, attractors, experiments, and Builder handoff.

## Conscious Exclusions

- Multiple simultaneous active Exploratory Stories per journey are still out of scope.
- Explorer does not become a hidden intent detector; the user activates the lens explicitly.
- Explorer does not mutate project state directly. Builder remains the delivery lens.
- The generated `docs/project/explorations/` handoff artifacts from validation are intentionally not part of this release. They remain local material for the next Soul Mode implementation.
- Advanced Explorer capabilities, richer web visibility, and Soul Mode itself remain future work.

## What We Learned

Explorer's value is not just that it can summarize uncertainty. Its value appears
when uncertainty becomes durable enough to return to, visible enough to trust,
and bounded enough not to become accidental implementation. The Soul Mode
validation made the evidence problem concrete: Builder does not only need a final
brief; it needs enough provenance to understand why the brief exists.

The Pi status-line leak also clarified that operating mode is a session property
when a runtime has session identity. A global fallback is useful for CLI
compatibility, but interactive runtimes need scoped mode state to remain honest.

## Next Horizon

The next visible horizon is Soul Mode. The local exploration artifacts generated
during validation should seed that work, but the implementation should begin from
Builder with a fresh delivery plan rather than being bundled into this Explorer
release. Explorer can now hold and promote that kind of discovery without forcing
it prematurely into construction.
