Palace Repair Console

Repair runbook for mempalace repair from-sqlite

MemPalace repair from-sqlite runbook

Build a backup-first MemPalace from-sqlite repair plan with verification, rollback, and proof receipt steps.

Open runbook Get the full recovery plan
A staged from-sqlite repair checklist with rollback notes. Live triage
Checkout Team annual
Search intent

A user has local memory data and wants a non-destructive repair path.

SERP gap

Search results tend to point to project commands or issue context, but not to an interactive recovery planner.

First screen result

Choose the store path, failure mode, and target client to generate a repair plan that starts with a snapshot.

Repair path

A staged from-sqlite repair checklist with rollback notes. This page is built for a developer who already has a MemPalace symptom and needs a safe next move.

  1. Confirm whether the target store is readable and whether writes are currently disabled.
  2. Create a timestamped backup and hash the backup before conversion.
  3. Run conversion in a temporary workspace and compare search counts before replacing anything.
  4. Keep the original store until multiple client sessions pass smoke checks.

Sample signal

mempalace repair --from-sqlite ./memory.db --dry-run

The full console stores the selected environment, likely cause, open risks, and planned verification checks as a proof receipt for team handoff.