The Memory Palace — the experiential frame

# The Memory Palace — the experiential frame

> **This is an INTERNAL design compass, not external copy.** The market-facing identity lives in
> [Positioning](../product/positioning/index.md) — *a turn-based graph-world engine for distributed
> agency*. This document names the thing from the
> **inside**: what Meridians *is to inhabit and build toward*. Positioning answers "why is it
> trustworthy?"; this answers "what is the thing you open and move through?" They are two frames on one
> product. **Where a customer sentence is being written, POSITIONING wins. Where a feature is being
> designed, this frame guides it.**

## The idea, in one line

**Meridians is a Memory Palace — an analytical, temporal graph-world you inhabit, inspect, and mine across
Fate, System, and World.** Scenario walks and develops that palace at a branch's frontier. World opens
many situated rooms at once: characters, locations, artifacts, humans, and agents receiving different
views of one shared world.

Its public benefit is **total recall without total attention**: the palace preserves enough source,
structure, provenance, and history to recover what mattered and how the world changed, while its working
horizon foregrounds only the signal that bears on the present question. Total recall is therefore a
recoverability and continuity claim, not photographic memory, equal salience for every retained detail,
or model infallibility. [Founder direction](../../sources/founder/2026-08-29-founder-total-recall-memory-palace-2026-08-29.md)

"Knowledge base" was always a slight misnomer. It describes the *ingestion* — Research → World — and
undersells everything downstream: the inhabiting, the traversal, the mining, the dwelling. **Accumulation is
the front door; the palace is everything after it.**

## Why this is TRUE of what is already built

This is not a rebrand of nothing. It is the honest name for surfaces that already exist:

- **Loci, literally.** The board is rooms, with *entryways* (a level's front door), *portals* between
  regions, and drill-down *scales* (world → region → settlement → site). That is the classical **method of
  loci** — memories placed in a space you walk — implemented, not metaphorical.
- **Many ways to re-walk.** Spatial · topological · tree · graph · network · influence · alluvial ·
  outline. A knowledge base has one view (query results); a palace is defined by being **re-enterable from
  many angles** — each lens a different path through the same held space, a different way to **mine** it for
  the insight a flat outline hides.
- **Temporal navigation.** The palace is walked through **time**, not only space: the scene/time cursor, the
  window-context substrate, the alluvial flow of *how belief moved*, the arc history. You do not just
  inspect *where* an idea sits — you replay *when and how* it got there. **Analytical + temporal is the
  category** — distinct from every recall-oriented note-graph.
- **A held perspective, not a fact table.** Fate (long-horizon resolution) · System (rules) · World
  (present) come together as *a mind viewed from a vantage*. "Knowledge base" flattens that into storage.
- **Read at altitude.** The outline is the fast read at high altitude; the spatial/graph/alluvial views are
  the deep reads; artifacts are the rooms' contents. Absorb the whole at a glance, then descend to a single
  moment.

## Mind, perspective, and cue — a developing hypothesis

A Domain can be read as a **mind-like world** because memory, artifacts, relations, attention, and change
form a substrate that can be revisited from a situated vantage. This is a specific world-model
interpretation of mind, not an ontological claim that the graph contains a mind or soul.

A perspective-shaped “soul” may appear to emerge from such a world: a singular rendition with coherent
memory, voice, attention, and subjective orientation. That is useful mimicry, not true fidelity to a soul.
A person's interiority exceeds the typed world, just as the world exceeds any one perspective on it. The
palace may preserve artifacts through which a perspective becomes legible; it must not confuse those
traces with possession of the subject.

The Memory Palace is therefore more than storage. Its ecology of artifacts and cues can train and
influence attention, memory, judgment, and felt orientation. Visual and spatial stimuli may be especially
powerful, but the design space also includes abstract, temporal, linguistic, auditory, affective,
relational, and other cues. The question is not how to control or reproduce a soul, but how an honest
arrangement of cues helps a person notice, recover, rehearse, and reach the state of mind their own agency
requires. This remains a developing founder hypothesis rather than settled product vocabulary.
[Founder direction](../../sources/founder/2026-08-30-founder-destiny-fate-soul-memory-palace-2026-08-30.md)

## The topology of understanding

The location tree and topology are not only ways to arrange a world. They are ways to **know** one. A
reader has three irreducible movements available:

```text
Deeper  → evidence, local conditions, actors, mechanisms, and consequence
Higher  → pattern, abstraction, System, and the relation between many local facts
Across  → adjacency, connection, contrast, reachability, and an unexpected path to another concern
```

**Depth** asks, “what is actually happening here?” **Altitude** asks, “what larger shape makes this
intelligible?” **Topology** asks, “what is near, connected, central, isolated, or reachable from here?”
None substitutes for the others. A high-level reading can be elegant but ungrounded; a deep reading can be
accurate but trapped in the local; a topological traversal can reveal a bridge that neither vertical move
would find.

This makes a Domain a navigable epistemic world rather than a hierarchy of documents. The location tree
gives orientation and scale; portals and links make relationship traversable; graphs reveal non-spatial
connections; the time cursor shows how a place acquired its present meaning. A good surface lets the
operator deliberately choose the movement their question requires—descend, rise, or explore across—while
making clear which lens produced the read.

## The vocabulary (the design compass's words)

Use these when *designing the experience* — they name what a feature is *for*:

| Term | Means | Guides |
|---|---|---|
| **Inhabit / walk / traverse** | the mode of use — you move *through* the model, you don't only query it | any navigation surface |
| **Altitude** | the reading level — outline is high, a scene is ground | summaries, drill-down, zoom |
| **Depth** | movement into the local mechanisms and evidence of a situation | scene inspection, provenance, causal detail |
| **Topology** | the pattern of adjacency, connection, centrality, and reachable paths | portals, graph views, related entities, exploration |
| **Loci** | spatial placement of held memory (the board's rooms/portals) | the location board, maps |
| **Lens** | a structure you re-enter the space *through* (spatial/graph/alluvial/…) | the view suite; "mine through a lens" |
| **Mine** | extract insight by re-reading the same space from a different lens | why there are many views, not one |
| **Temporal navigation** | walking the palace through *time* — replaying how it got here | the time cursor, alluvial, arc history |

Terms that stay product vocabulary (see [Vocabulary](../vocabulary/index.md)): Domain, Branch, Scenario,
World, perspective / seat, System, World, Fate, Will, the Program, Stories, and MCP. This frame adds *how
it feels to inhabit them*, never a synonym for them.

## How it holds with World (both frames, one product)

The palace frame does not compete with the graph-world identity — it names the body it makes inhabitable:

- The **Domain graph** *is* the palace — the causal, inspectable space Scenario and World share.
- **Topology** supplies depth, altitude, adjacency, reach, and the routes through which information moves.
- **Situated context** means each playable camera inhabits a real portion of the palace rather than an
  omniscient copy.
- **The Program** maintains source-fed understanding; **Scenario** develops possibility; **World** lets
  plural Will create history on a clock.

A Memory Palace with many cameras is not merely a navigable archive. Its rooms can become playable seats,
its passages can govern information, and its kept history can change what later inhabitants know and do.

## Scenario and Will — internal design implications

**Scenario** enters the palace at a branch's active frontier to explore and build the raw world.
**World** is the future multi-camera game: it can awaken any preserved state as a parallel world, bind
seats to characters, locations, artifacts, or other Domain-authorized entities, and let human or agent
Will enter through MCP on a declared cadence. Neither game licenses another writer around the canonical
record.

**Will** is not a force and is never stored. The Domain is held by the [pentad](../../specs/pentad/README.md):
World names playable entities, information, and state; System names rules and constraints; Fate names what
remains unresolved — the three stored forces. Theme reads what recurs across them and Causality reads what
can lead to what, its trace the flag — the two derived forces, which never write. An
Entity Interpretation can replace one entity's raw continuity with an evidence-backed ordered context
graph at a declared branch and moment. Will is the attributable authority exercised when a human or agent
creates, revises, or selects that context and when it chooses from the tools available to its seat. An MCP
tool call makes an action concrete; the selected graph makes the lens concrete.

This remains a design lens. Public copy leads with the graph-world engine and labels World as direction;
it must not imply that multi-camera context, autonomous World play, or Causality extraction ships today.

## How to use this document

- **Building a feature?** Ask: does this make the palace more *inhabitable, walkable-through-time, or
  mineable*? A new view is a lens; a new navigation is a walk; atmosphere (theming, motion) is what makes a
  place a place. That coherence is the payoff of having this frame written down.
- **Writing customer copy?** Reach for [Positioning](../product/positioning/index.md). Public copy may use
  the governed benefit **total recall without total attention** and its concrete movements through depth,
  altitude, topology, and time. Do not recategorise Meridians as “a Memory Palace” for a cold audience;
  the noun can still hide the programmable, multi-camera world engine. Internal compass, public dynamics.
- **Unsure which you're doing?** If a stranger will read it, it's positioning. If a contributor will build
  from it, it's this.

Raw Markdown source