Files

T

Igor Lins e Silva dfb22f5345 docs: add VitePress documentation site

- 22 content pages across Guide, Concepts, and Reference sections
- Custom indigo/cyan theme with Lucide icons and Mermaid diagrams
- GitHub Actions workflow for GitHub Pages deployment
- Live preview: https://mempalace-docs.netlify.app/

2026-04-09 19:41:08 -03:00

3.8 KiB

Raw Blame History

The Palace

Ancient Greek orators memorized entire speeches by placing ideas in rooms of an imaginary building. Walk through the building, find the idea. MemPalace applies the same principle to AI memory.

Structure

Your conversations are organized into a navigable hierarchy:

graph TD
    subgraph wing_person["WING: Person"]
        direction TB
        RA["Room A"] -- hall --> RB["Room B"]
        RA --> CA["Closet"]
        CA --> DA["Drawer (verbatim)"]
    end

    subgraph wing_project["WING: Project"]
        direction TB
        RA2["Room A"] -- hall --> RC["Room C"]
        RA2 --> CA2["Closet"]
        CA2 --> DA2["Drawer (verbatim)"]
    end

    RA -.->|tunnel| RA2

    style wing_person fill:#1e1b4b,stroke:#4f46e5,color:#e0e7ff
    style wing_project fill:#164e63,stroke:#06b6d4,color:#cffafe
    style RA fill:#312e81,stroke:#6366f1,color:#e0e7ff
    style RB fill:#312e81,stroke:#6366f1,color:#e0e7ff
    style CA fill:#3b0764,stroke:#8b5cf6,color:#f3e8ff
    style DA fill:#0f766e,stroke:#14b8a6,color:#ccfbf1
    style RA2 fill:#155e75,stroke:#22d3ee,color:#cffafe
    style RC fill:#155e75,stroke:#22d3ee,color:#cffafe
    style CA2 fill:#3b0764,stroke:#8b5cf6,color:#f3e8ff
    style DA2 fill:#0f766e,stroke:#14b8a6,color:#ccfbf1

Components

Wings

A person or project. As many as you need.

Every project, person, or topic gets its own wing in the palace. Wings are the top-level organizational unit.

Rooms

Specific topics within a wing. Examples: auth-migration, graphql-switch, ci-pipeline.

Rooms are named ideas. They're auto-detected from your folder structure during mempalace init, and you can create additional rooms manually.

Halls

Halls are the conceptual categories that describe how related memories connect within a wing:

hall_facts — decisions made, choices locked in
hall_events — sessions, milestones, debugging
hall_discoveries — breakthroughs, new insights
hall_preferences — habits, likes, opinions
hall_advice — recommendations and solutions

Tunnels

Connections between wings. When the same room appears in different wings, the graph layer can treat that as a cross-wing connection.

wing_kai       / hall_events / auth-migration  → "Kai debugged the OAuth token refresh"
wing_driftwood / hall_facts  / auth-migration  → "team decided to migrate auth to Clerk"
wing_priya     / hall_advice / auth-migration  → "Priya approved Clerk over Auth0"

Same room. Three wings. The graph can use that shared room name as a bridge.

Closets

Closets are the summary layer in the broader MemPalace vocabulary: compact notes that point back to the original content. In the current implementation, the main persisted storage path is still the underlying drawer text plus metadata.

Drawers

The original stored text chunks. This is the primary retrieval layer used by the current search and benchmark flows.

Why Structure Matters

Tested on 22,000+ real conversation memories:

Search scope	R@10	Improvement
All closets	60.9%	baseline
Within wing	73.1%	+12%
Wing + hall	84.8%	+24%
Wing + room	94.8%	+34%

The practical point is that structure improves retrieval. In the project benchmarks, narrowing the search scope by wing and room outperformed searching the entire corpus at once.

The palace supports graph traversal across wings:

MCP tool: mempalace_traverse
  arguments: { "start_room": "auth-migration" }
  → discovers rooms in wing_kai, wing_driftwood, wing_priya

MCP tool: mempalace_find_tunnels
  arguments: { "wing_a": "wing_code", "wing_b": "wing_team" }
  → auth-migration, deploy-process, ci-pipeline

This is the navigation story: shared room structure gives the model more than one way to reach relevant context.

3.8 KiB Raw Blame History