Why this page exists #

Honors record · Mirror Runtime v1 standalone checkpoint

This page captures the first fully usable Mirror Runtime product surface: a detached runtime with its own CLI, service, gateway, chat engine, provider runtime, canon workflow, user workspace, Monk assistance, sync layer, and operator observability. It is a system diagram for builders, operators, and future ToadAid records.

Runtime truth
Mirror owns the operator-facing runtime path
Knowledge truth
Canon and workspace stay separated by design
Human truth
Tasks, reminders, heartbeat, and Monk assistance now live in the pond

Mirror Runtime v1 Diagram #

Canonical runtime flow · operator to model, with protected canon and workspace zones
                           ┌──────────────────────┐
                           │      Operator /      │
                           │        User          │
                           └──────────┬───────────┘
                                      │
                     ┌────────────────┼────────────────┐
                     │                │                │
                     ▼                ▼                ▼
              ┌────────────┐   ┌────────────┐   ┌──────────────┐
              │ Mirror CLI │   │ Mirror Web │   │ Mirror HTTP  │
              │serve/status│   │  Console   │   │   Clients    │
              │sync/verify │   │            │   │              │
              └─────┬──────┘   └─────┬──────┘   └──────┬───────┘
                    │                │                 │
                    └────────────────┴─────────────────┘
                                     │
                                     ▼
                          ┌──────────────────────┐
                          │    Mirror Service    │
                          │ /mirror/* + health   │
                          │ /status + console    │
                          └──────────┬───────────┘
                                     │
                                     ▼
                          ┌──────────────────────┐
                          │    Mirror Gateway    │
                          │ tools + chat routes  │
                          └──────────┬───────────┘
                                     │
                  ┌──────────────────┼──────────────────┐
                  │                  │                  │
                  ▼                  ▼                  ▼
        ┌────────────────┐  ┌────────────────┐  ┌────────────────┐
        │ Tool Registry  │  │  Chat Engine   │  │ Observability  │
        │ mirror.* tools │  │ request/prompt │  │ metrics/diag   │
        │ + verify-lore  │  │                │  │ health/status  │
        └───────┬────────┘  └────────┬───────┘  └────────────────┘
                │                    │
                │                    ▼
                │          ┌──────────────────────┐
                │          │  Reflection Engine   │
                │          │ themes/symbols/review│
                │          └──────────┬───────────┘
                │                     │
                │                     ▼
                │          ┌──────────────────────┐
                │          │ Retrieval + Context  │
                │          │ canon + memory order │
                │          └──────────┬───────────┘
                │                     │
                │                     ▼
                │          ┌──────────────────────┐
                │          │ Mirror Provider RT   │
                │          │ auth/request/response│
                │          └──────────┬───────────┘
                │                     │
                │                     ▼
                │             ┌──────────────┐
                │             │    Model     │
                │             └──────────────┘
                │
                ▼
   ┌──────────────────────────────────────────────────────────────┐
   │                    Mirror Capability Layer                   │
   │                                                              │
   │ Canon tools:                                                 │
   │   find-scroll / canon-fact / interpret / forge / commit      │
   │                                                              │
   │ User tools:                                                  │
   │   task.* / reminder.* / heartbeat.*                          │
   │                                                              │
   │ Monk tools:                                                  │
   │   monk.context / monk.next / monk.resume / monk.followup     │
   └──────────────────────────────────────────────────────────────┘

   ┌──────────────────────────┐   ┌──────────────────────────────┐
   │      Canon Layer         │   │      User Workspace Layer    │
   │                          │   │                              │
   │ Scrolls / Symbols        │   │ Profile / Preferences        │
   │ Lore Graph / Review      │   │ Tasks / Reminders            │
   │ Validation / Commit      │   │ Heartbeat / Sessions         │
   │ Sync / Canon Index       │   │ Monk Context / Notes         │
   └──────────────────────────┘   └──────────────────────────────┘

Runtime layers #

Mirror v1 separated into interface, runtime, intelligence, and state
🖥️
Interface Layer

Mirror CLI, Mirror Console, and HTTP clients are the operator-facing doors into the system.

⚙️
Runtime Layer

Mirror Service, Gateway, Tool Registry, and Chat Engine route requests and keep the standalone product surface coherent.

🧠
Intelligence Layer

Reflection, retrieval, memory ordering, and provider execution shape how Mirror thinks before the model speaks.

📚
State Layer

Canon remains shared truth; Workspace remains personal state. They are intentionally separated.

Canon and Workspace are separate by design #

One of the most important architectural rules in Mirror Runtime

Canon Layer

Shared truth for everyone. Canon is protected through interpretation, drafting, review, commit, validation, and sync rules.

  • Scroll corpus
  • Symbol registry
  • Lore graph
  • Review + conflict detection
  • Commit + validation pipeline

User Workspace Layer

Personal state for one traveler. Workspace supports daily utility without rewriting shared truth.

  • Profile + preferences
  • Tasks + reminders
  • Heartbeat state
  • Sessions + notes
  • Monk context + follow-up notes

Mirror and Monk can use both layers. Personal state never becomes canon unless it travels through the explicit canon workflow.

Core flows #

The three most important flows in Mirror Runtime v1
💬
Chat Flow

CLI / Console / API → Service → Gateway → Chat Engine → Reflection → Retrieval/Memory → Provider Runtime → Model, with standalone /mirror/health and /mirror/status for operator checks.

📜
Canon Flow

interpret → forge → review → commit, with validation, conflict checks, atomic writes, and index refresh.

🧘
Daily Utility Flow

workspace → tasks → reminders → heartbeat → Monk follow-up.

Canonical product surface #

What counts as Mirror Runtime v1 from the user/operator perspective
⌨️
mirror CLI

mirror serve, mirror status, mirror sync ..., mirror verify-lore, canon commands, workspace utilities, Monk assistance, and stable JSON output for automation.

🌐
mirror service

Canonical HTTP product surface under /mirror/*, plus /mirror/health, /mirror/status, sync, console, metrics, and diagnostics.

🪟
mirror console

Lightweight web surface for chat, tools, lore graph, tasks, reminders, heartbeat, Monk assistance, sync, and ops visibility.

📡
mirror sync

Peer registry, canon update exchange, graph freshness metadata, and safe validated pull behavior for Mirror nodes.

Standalone operator surface #

The final canonical Mirror v1 commands and health surface after consolidation
Serve
mirror serve
Status
mirror status
Sync
mirror sync peers|updates|announce|pull
Canon verify
mirror verify-lore
Health
/mirror/health
Runtime status
/mirror/status

Compatibility-only surface #

Present in the repository, but not part of the canonical standalone Mirror v1 surface. These paths remain for compatibility, migration, or advanced operator workflows only.
Compatibility / advanced operator paths
- doctor
- passport
- telemetry replay / telemetry index / telemetry query / telemetry reflect
- legacy wrappers: server.ts, brain-chat.ts, mirror_tools_api.ts, mirror-cli.ts, console_server.ts

Archived / non-standalone built-ins
- mirror.echo
- chain skill family

These remain by design for compatibility, migration, or advanced workflows,
but they are not part of the primary standalone Mirror product identity.

Why this matters #

Why Mirror Runtime v1 is more than just another AI wrapper

Mirror Runtime v1 is a detached AI runtime with a protected truth layer, a personal workspace layer, a daily utility layer, a reflective assistant layer, and a network-ready sync layer. It can be extended without collapsing canon into personal memory, and it can grow toward Mirror OS without losing its architectural center.

Truth
Canon-first and review-governed
Person
Workspace-backed and local-first
Care
Tasks, reminders, heartbeat, Monk assistance
Network
Node sync and observability ready