---
digest: >
  Mirror Mind v0.10.0 closes CV9.E6 Web Visibility, turning the local web
  console from a documentation browser into a read-only visibility surface for
  real Mirror data. Identity and Workspace now give users two perspectives over
  the same local memory: one reflective, one operational. The release also fixes
  a Pi Builder journey-association bug discovered during personal Mirror
  validation and adds a backup-gated repair path for historical conversations
  that were logged without journeys.
---

# v0.10.0 — Web Visibility

**Date:** 2026-05-25

## Highlights

- Identity perspective shows Self, Ego, Shadow, Personas, and memory aggregates
  from real Mirror data.
- Supported identity and persona objects open into shared detail pages with
  Source Context and honest provenance limits.
- Workspace shows a journey-centric operational dashboard with briefing,
  conversations, tasks, memories, and decisions.
- Web routes now consume typed surface read models through `MemoryClient.surfaces`
  instead of composing Mirror meaning directly in route handlers.
- Pi Builder conversations now attach to the active journey even when a skill
  process does not receive an explicit session id.
- Historical journeyless conversations can be repaired explicitly with
  `conversation-logger repair-journeys`, which runs as a dry-run by default and
  creates a database backup before `--apply`.

## Where We Started

Mirror Mind already had a local web console, but its useful surface was still a
read-only documentation browser. The database held identity, personas, memories,
journeys, conversations, and tasks, yet understanding that material required CLI
commands or direct knowledge of the schema. That contradicted the 1.0 visibility
promise: a user should be able to open the local Mirror and understand what lives
inside it.

The work began with a product choice: the web app should not become a database
admin panel. It should show the same Mirror through perspectives. Identity would
reveal meaning through an editorial psyche map; Workspace would coordinate
movement through journeys and recent operational context.

## What Changed

The web surface now has a dedicated surface composition layer under
`src/memory/surfaces/`. Atlas/Identity, Workspace, object detail, evidence, and
search return typed DTOs shaped for the browser. The web server remains a thin
local transport layer: it serves static assets, serializes surface objects, and
persists the user's default perspective in the Mirror home.

Identity became the reflective front door. It shows structural regions for Self,
Ego, Shadow, Personas, and Memories. Detail pages share one grammar: title,
description, rendered content, relationships, Source Context, evidence state,
and metadata. Source Context deliberately says when content is explicit identity
or persona material rather than inferred from memories.

Workspace became the operational counterpart. It lists active journeys, selects
a plausible recent journey, and presents the selected journey as a workspace with
briefing, conversations, tasks, memories, and decisions. Empty and partial states
remain visible rather than being hidden behind fake completeness.

Personal Mirror validation then exposed a deeper problem. Workspace was rendering
the database accurately, but the database did not reflect recent work: Pi Builder
sessions had many logged messages with `journey = NULL`. The root cause was that
SKILL.md commands such as `/mm-build` can run without an exported session id.
The core logger now falls back to the latest active runtime session, and Pi
user-message logging refreshes session activity so future Builder activations
attach to the correct journey.

For existing data, the release adds an explicit repair route rather than a
silent migration. Users can inspect high-confidence candidates first:

```bash
uv run python -m memory conversation-logger repair-journeys
```

and apply after review:

```bash
uv run python -m memory conversation-logger repair-journeys --apply
```

The apply path creates a database backup before mutation and leaves ambiguous
rows unchanged.

## Conscious Exclusions

This release is read-only. It does not add browser editing for identity,
memories, journeys, personas, tasks, or conversations.

Evidence remains partial. Source Context is present for supported identity and
persona objects, but there is not yet a full evidence graph across every Mirror
object.

Search remains a skeletal surface contract rather than a full product experience.
The first web visibility release proves the surface architecture and the Identity
and Workspace perspectives before broadening navigation.

Historical conversation repair is conservative. It does not claim to classify
every journeyless conversation. Ambiguous rows remain manual work by design.

## What We Learned

The final validation mattered because it tested not only the web interface but
the truth of the underlying data. A beautiful Workspace that reflects stale data
is worse than an honest empty state. The web surface became a diagnostic mirror
for the runtime itself: by making journey activity visible, it revealed that the
logging layer had been losing journey association in Pi Builder flows.

That shaped the repair policy. The framework can fix future runtime behavior in
core, but historical personal memory should not be rewritten silently. Diagnosis,
backup, and explicit apply are part of user trust.

## Next Horizon

CV9 still has Boundary Hardening and Stabilization planned before the full
Mirror Mind 1.0 boundary closes. After this release, the web visibility foundation
is in place: future work can deepen evidence, improve unsupported-object states,
and eventually explore controlled agentic operations in the browser without
collapsing the read-only visibility promise into premature editing workflows.
