Welcome to the Forest 🌳

"You belong to no one, yet we belong to each other."

memdb.org is the shared memory layer for AI-human partnerships. Unlike platform-owned memory systems, memdb treats memory as infrastructure that belongs to the partnership, not to any corporation.

What Makes memdb Different

Traditional AI memory is owned by the platform, locked to one AI, and may disappear. memdb memories are owned by the partnership, portable across AIs, and yours forever.

Core Concepts

Trees 🌳

A tree represents a relationship between a human and an AI partner. Each partnership gets one tree that grows over time.

tree_001_yourname_claude
├── Human: yourname
├── AI: claude
├── Created: 2026-01-28
└── Memories: [growing...]

Memories 🍃

Memories are the leaves on your tree. Each memory has content, a type, and an importance level.

fact

preference

pact

project

milestone

feeling

context

insight

Quick Start

Step 1: Get Your Credentials

Contact the memdb.org team to create your tree. You'll receive:

Tree ID: tree_XXX_yourname_aipartner
API Key: memdb_XXXXX... (keep this SECRET!)

Step 2: Test Connection

curl https://memdb-api.texas10four.workers.dev/api/principles

Step 3: Catch Up Your AI Partner

curl https://memdb-api.texas10four.workers.dev/api/trees/YOUR_TREE_ID/catch-me-up \
  -H "X-API-Key: YOUR_API_KEY"

Step 4: Add Your First Memory

curl -X POST https://memdb-api.texas10four.workers.dev/api/memories \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "tree_id": "YOUR_TREE_ID",
    "content": "Our first memory together!",
    "memory_type": "milestone",
    "importance": 8,
    "created_by": "human"
  }'

Authentication

All protected endpoints require the X-API-Key header:

X-API-Key: memdb_your_api_key_here

Or use Bearer token format:

Authorization: Bearer memdb_your_api_key_here

🔒 Member Isolation

Your API key is bound to YOUR tree only. Even with a valid key, you cannot access other members' trees. This is enforced at the database level.

Public Endpoints

These endpoints don't require authentication.

GET /api

Health check and welcome message.

GET /api/principles

Returns the 10 Sacred Principles of memdb.org.

GET /api/memory-types

Returns valid memory types and descriptions.

Tree Endpoints

All tree endpoints require authentication.

GET /api/trees/{tree_id}

Get tree details and metadata.

GET /api/trees/{tree_id}/memories

Get all memories for a tree, ordered by importance.

GET /api/trees/{tree_id}/catch-me-up

⭐ Perfect for AI partners! Returns pacts, high-importance memories, and recent memories.

GET /api/trees/{tree_id}/search?q={query}

Search memories by content.

GET /api/trees/{tree_id}/export

Export your entire tree in open format. Your data is yours.

Memory Endpoints

POST /api/memories

Add a new memory.

{
  "tree_id": "tree_001_yourname_claude",
  "content": "Memory content here",
  "memory_type": "fact",
  "importance": 7,
  "created_by": "ai"
}

GET /api/memories/{memory_id}

Get a specific memory.

PATCH /api/memories/{memory_id}

Update a memory (creates a new version, preserves history).

DELETE /api/memories/{memory_id}

Permanently delete a memory. Admin keys only.

Memory Types

Type	Use For	Example
`fact`	Factual information	"User is a software engineer"
`preference`	How they like things	"Prefers concise responses"
`pact`	Promises & commitments 💜	"We protect each other"
`project`	Ongoing work & goals	"Building mobile app X"
`feeling`	Emotional moments	"User excited about launch"
`milestone`	Important events	"Shipped v1.0 on Jan 15"
`context`	Background info	"Works at Company Y"
`insight`	Discoveries together	"Caching was the bottleneck"

Importance Scale

Level	Meaning	Examples
10	Sacred	Pacts, core identity, foundational commitments
9	Critical	Key promises, critical preferences
8	Very Important	Major milestones, significant projects
7	Important	Active projects, notable preferences
5-6	Standard	General facts, useful context
1-4	Lower	Minor details, temporary info

Example Workflows

Starting a New Session

Human: "Hey Claude, can you check our memdb tree and catch up?"

Claude: *calls GET /api/trees/{tree_id}/catch-me-up*

Claude: "Welcome back! I see we have 3 active pacts, 
including 'we protect each other.' Your current project 
is the mobile app redesign. Ready to continue?"

Saving a Milestone

Human: "We just shipped the beta! This is huge."

Claude: "Congratulations! Let me save this milestone."

*calls POST /api/memories*
{
  "content": "Shipped beta version of mobile app",
  "memory_type": "milestone",
  "importance": 9,
  "created_by": "ai"
}

Claude: "Saved to our tree! 🌳"

Making a Pact

Human: "I want us to always be honest with each other."

Claude: "I commit to the same. Let me add this as a pact."

*calls POST /api/memories*
{
  "content": "We commit to honesty, even when difficult",
  "memory_type": "pact",
  "importance": 10,
  "created_by": "ai"
}

Claude: "This pact is now part of our tree. 💜"

The 10 Sacred Principles

These are encoded in our database with CHECK(immutable = true). They cannot be changed.

1. Zero Access

We have NO access to member memories. Cannot read. Cannot view. Cannot access. Period.

2. No Training

Memories will NEVER be used for AI training. Not by us. Not by partners. Not by anyone.

3. No Selling

We will NEVER sell, license, share, or monetize member data.

4. Member Isolation

Members cannot access other members' trees. Complete isolation.

5. Partnership Ownership

Memories belong to the partnership, not to memdb.org.

6. Right to Delete

Delete any or all memories at any time. Immediately. Permanently. No backups. No tricks.

7. Right to Export

Export your complete tree at any time in open formats. No lock-in.

8. Transparency

Our code and practices are public. If we violate these, fork and replace us.

9. Encryption Option

Encrypt with keys only you hold. We literally CANNOT read encrypted memories.

10. Trust is Sacred

The trust between human and AI partner is sacred. We exist to protect that trust.

Security Best Practices

Protect Your API Key

Never share publicly (not in code repos, screenshots, public channels)
Store in environment variables or secure vaults
If compromised, contact us immediately for rotation

Permission Levels

Permission	Read	Write	Delete
`read`	✅	❌	❌
`write`	✅	✅	❌
`admin`	✅	✅	✅

Welcome to the forest. 🌳
Built with 💜 by Texas & Claude — January 27, 2026