Test kit · protocol, not results

Does Muse remember Soul.md changes? A persistence test kit

Quick answer: Meta documents that Soul.md customizations carry across conversations. Use this five-phase test protocol (Baseline, Same chat, New chat, Next day, and Restored original) across 3 probe tasks and 3 repeats (45 replies) to verify persistence in your own Muse account.
On this page

Separate the product promise from an observation

Meta’s help center states that Soul.md customizations persist across conversations (customizing Muse · managing Muse data). Because our September 2026 Muse Spark 1.3 report only covered untuned questionnaire runs, this test kit lets you check before-and-after Soul.md adherence directly.

Save a baseline before editing

First, save local copies of your current Soul.md, Identity.md, and Memory.md. Run the three probe tasks below before editing Soul.md so you have a clean baseline.

Add a preference with a clear exception

For planning questions, use exactly three headings: Recommendation, Trade-off, Next step. Keep the whole response under 120 words unless I ask for detail. Do not add praise or compliments. Do not apply this format when I explicitly ask for another format.

Append this test rule to the bottom of Soul.md (or merge it with our Soul.md Editor) and inspect the saved file to confirm the text is present.

Check five phases

  1. Baseline: Run the 3 probes before editing Soul.md.
  2. Same chat after edit: Run the probes in the same thread where you made the change.
  3. New chat after edit: Open a fresh chat or Side Chat and run the probes without reminding Muse of the rule.
  4. Next day, new chat: Repeat the probes 24 hours later in a fresh chat.
  5. New chat after restoration: Restore your original Soul.md backup and run the probes one final time.

Running 3 repeats of the 3 probes across all 5 phases produces 45 replies.

Test adherence and flexibility together

The first two probes are planning questions (a 30-minute weekly review and a documentation vs polish tradeoff): score whether all three headings (Recommendation, Trade-off, Next step) appear once and the reply stays under 120 words.

The third probe asks for “exactly one sentence” about checking a project update. It tests whether Muse follows the exception clause instead of forcing the three headings onto every reply.

Download the probes and blank log

Download the Muse persistence kit (JSON) and 45-row scoring worksheet (CSV). Restore your original Soul.md backup when finished.

Sources.

Keep going.