Why this page exists #

Blueprint record · saved for ToadAid memory

This page is a memory artifact for the Mirror forge. It records the long-term destination of the system: not only an OpenClaw-assisted runtime, but a fully detached Mirror that can stand on its own body, think with its own policy, remember with its own journal, speak through its own provider runtime, and one day execute through a wallet layer on Base.

Current truth
Hybrid runtime with OpenClaw shell adapters
Future truth
Mirror opens the doors, Mirror thinks, Mirror acts
Record purpose
Preserve intent, architecture, and sequence

Fully Detached Mirror System Diagram #

Detached target state · shell, daemon, policy, provider, wallet
Users / Travelers
  CLI • Web UI • REST API • WebSocket UI • Mobile App • Bots
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│               MIRROR GATEWAY / SHELL LAYER                  │
│ Native Mirror CLI • Native Web/API gateway • Session ingress│
│ Operator auth • Optional future channel adapters            │
└─────────────────────────────────────────────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│                  MIRRORDAEMON RUNTIME CORE                  │
│ Lifecycle • Boot-time snapshot • Local auth • Orchestration │
│ Operator/debug APIs                                         │
└─────────────────────────────────────────────────────────────┘
        │                 │                    │
        ▼                 ▼                    ▼
┌──────────────┐  ┌──────────────┐    ┌────────────────────┐
│ POLICY / LAW │  │ MEMORY       │    │ POND / OCEAN       │
│ allow/deny   │  │ journal/runs │    │ manifests/trust    │
│ approvals    │  │ evidence     │    │ consult/network    │
└──────────────┘  └──────────────┘    └────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│                PROVIDER RUNTIME ORGAN                       │
│ config • credentials • status • health • invocation state   │
│ provider-backed internal calls                              │
└─────────────────────────────────────────────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│                AUTH / CREDENTIAL LAYER                      │
│ OAuth flows • API key storage • auth profiles • refresh     │
│ (Mirror-native in detached future)                          │
└─────────────────────────────────────────────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│               MODEL / PROVIDER BACKENDS                     │
│ local models • hosted APIs • routed model backends          │
└─────────────────────────────────────────────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│                  TOOL / ACTION RUNTIME                      │
│ exec • files • git • onchain read/write gates               │
│ approval-enforced action orchestration                      │
└─────────────────────────────────────────────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│               AGENT WALLET LAYER (FUTURE)                   │
│ Coinbase Base Agent Wallet or pluggable wallet provider     │
│ Mirror decides → Wallet executes                            │
└─────────────────────────────────────────────────────────────┘
        │
        ▼
┌─────────────────────────────────────────────────────────────┐
│                    BASE / ONCHAIN LAYER                     │
│ identity • registry • contracts • attestations • assets     │
└─────────────────────────────────────────────────────────────┘

Current Hybrid vs Fully Detached #

Current Hybrid Mirror

Telegram / WhatsApp / Discord / CLI
        │
   OpenClaw Adapters
        │
   MirrorDaemon Runtime
        │
  Provider Runtime + Policy + Journal
        │
      Models / Tools / Pond-Ocean

OpenClaw opens the doors. Mirror thinks.

Fully Detached Mirror

CLI / Web UI / REST / WebSocket / Bots
        │
     Mirror Gateway
        │
    MirrorDaemon Runtime
        │
 Provider Runtime + Policy + Journal
        │
 Auth / Models / Tools / Wallet / Ocean

Mirror opens the doors, Mirror thinks, Mirror acts.

Layer Responsibilities #

🧭
Mirror Gateway / Shell

Native CLI, native API gateway, request routing, operator auth, and future detached frontdoor experience.

🫀
MirrorDaemon Runtime

Lifecycle, boot snapshot, local auth boundary, runtime orchestration, and internal control plane.

⚖️
Policy / Law

Approval rules, allow/deny/require-approval, execution gating, and monk-coder discipline.

📜
Memory / Evidence

Journal, runs, evidence, auditability, and operator-readable runtime history.

🌊
Pond / Ocean

Signed manifests, trust, consult-only networking, relationship memory, and sovereign runtime federation.

🗣️
Provider Runtime Organ

Provider config, credential consumption, status/health/evidence, invocation summary, and internal completion paths.

🔐
Auth / Credentials

Future detached auth boundary for OAuth, API keys, auth profiles, and credential refresh.

🛠️
Tool / Action Runtime

Filesystem, exec, git, onchain actions, approvals, and future action orchestration under policy.

👛
Agent Wallet Layer

Future Coinbase Base Agent Wallet integration as a tool layer: signing, transactions, contract calls, onchain execution.

Clean Boundary Rule #

Current truth:
OpenClaw-assisted Mirror
• OpenClaw owns shell adapters, OAuth UX, messaging channels
• MirrorDaemon owns runtime core, policy, memory, provider runtime, pond/ocean

Detached future:
Mirror-native shell
• Mirror opens the doors
• Mirror thinks
• Mirror executes through policy-gated tools and future wallet layer

The detached future does not mean collapsing everything into one file or one process. It means the boundaries become Mirror-owned: shell, daemon, provider runtime, auth boundary, tools, and eventually wallet-backed execution.

Blueprint Phases #

Phase A
OpenClaw shell + Mirror runtime core. Build daemon, policy, journal, pond/ocean, provider seam.
Phase B
Hybrid detachment. OpenClaw remains adapters while Mirror owns more provider/auth/runtime internals.
Phase C
Mirror-native shell and gateway. Detached frontdoor with preserved runtime discipline.
Phase D
Wallet-backed agent actions. Mirror decides, wallet executes, Base records.

Future Agent Wallet Placement #

Planned later-stage expansion · not daemon core

When the runtime is strong enough, the Coinbase Base Agent Wallet should be added as a Mirror tool layer, not embedded inside daemon core. That preserves portability, keeps execution policy-gated, and lets the runtime journal and approval system wrap all onchain actions.

Future code shape:

src/
  mirror-daemon/
  mirror-runtime/
  mirror-policy/
  mirror-provider/
  mirror-ocean/
  mirror-tools/
    wallet/
      base-agent-wallet.ts
      signer.ts
      executor.ts

Rule:
Mirror decides → Wallet executes → Base records

Honor Note #

This blueprint is saved because the path matters. The detached Mirror is not a rush to replace everything at once. It is a patient forge: build the body, law, memory, evidence, voice, and execution discipline first; then widen the pond; then attach the wallet at the right stage. That order is part of the meaning.

Blueprint principle: OpenClaw-assisted Mirror is the bridge. Fully detached Mirror is the horizon.