An AI that actually knows you — and gets better the longer you work together.

Version: v0.1.0

Most AI tools start every conversation from zero — you re-explain context, re-establish preferences, re-pitch the project. UMS treats that as a structural problem. It's a personal cognitive infrastructure — a second mind — that observes during real work and writes a structured update at the end of each session to a persistent page Claude reads first thing every time.

Two dimensions deepen with use:

• What Claude knows about your world — people, projects, decisions, patterns
• How Claude calibrates to you — directness, depth, register, pacing

For Claude.ai users who want their AI to compound understanding across sessions. Notion + MCP setup required, ~15–30 min to install.

The Mind layer — task/work domain only, Claude.ai as the primary path. Foundation for what comes next; the rest is deferred.

In v0.1:

• One UMS page — 8 sections (Partnership, Situation, Learning Edge, People, Recent Decisions, Recent Sessions, Map, Tasks DB embed)
• 6 knowledge subpages demand-loaded via Map triggers — People, Patterns, Company & Products, Reference, Journey, Archives
• Tasks DB + task pages — execution layer foundation
• Three skills — ums-init (setup), ums-session (orient), ums-capture (observe, persist, curate)

Deferred: personal-context layer, project-context layer, async maintenance, user-facing eval toolkit, additional interfaces.

You can't run autonomously for a user the system doesn't yet know. v0.1 builds the substrate.

At session start — Main page loads silently. Claude has the active task, recent decisions, the calibration rules you've established. The conversation begins mid-context.

Mid-session — Corrections, observations, and pattern signals stage silently. A correction made today doesn't need to be made again tomorrow.

End of conversation — Claude assembles a structured update from the session: Learning Edge candidates, Situation rewrite, Calibration changes, task-page updates, lifecycle transitions. The session becomes substrate for the next one.

┌─────────────────────────────────────────────────────────────────┐
│                             User                                │
└──────────────────────────┬──────────────────────────────────────┘
                           │
┌──────────────────────────▼──────────────────────────────────────┐
│                        Claude.ai                                │
│  ┌────────────────────────────────────────────────────────┐     │
│  │ Custom Instructions (posture + skills + page IDs)      │     │
│  ├────────────────────────────────────────────────────────┤     │
│  │ ums-session  (orient at session start)                 │     │
│  │ ums-capture  (observe, persist, curate)                │     │
│  │ ums-init     (one-time setup, manual-only)             │     │
│  └────────────────────────────────────────────────────────┘     │
└──────────────────────────┬──────────────────────────────────────┘
                           │
                           │ Read (session start, demand-load)
                           │ Write (EOC batch, user-confirmed)
                           │
┌──────────────────────────▼──────────────────────────────────────┐
│                           Notion                                │
│  ┌──────────────────────────────────────────────────────┐       │
│  │ UMS Main Page (~4K tokens)                           │       │
│  │   §1 Partnership    §5 Recent Decisions              │       │
│  │   §2 Situation      §6 Recent Sessions               │       │
│  │   §3 Learning Edge  §7 The Map                       │       │
│  │   §4 People         §8 Tasks DB (embed)              │       │
│  └──────────────────────────────────────────────────────┘       │
│  ┌──────────────────────────────────────────────────────┐       │
│  │ Subpages (6, demand-loaded via Map triggers)         │       │
│  │   People • Patterns • Company & Products •           │       │
│  │   Reference • Journey • Archives                     │       │
│  └──────────────────────────────────────────────────────┘       │
│  ┌──────────────────────────────────────────────────────┐       │
│  │ Tasks DB + Task Pages — The Work (execution layer)   │       │
│  │ Demand-loaded per task                               │       │
│  └──────────────────────────────────────────────────────┘       │
└─────────────────────────────────────────────────────────────────┘

Read — main page at session start; subpages on Map-triggered demand; task pages per task.

Write — EOC batch → Notion, user-confirmed. Session Buffer triggers a mid-session save on long sessions to protect staged observations against context compaction.

Notion-bindable but not Notion-bound — storage swaps when a unified knowledge layer arrives. Skill files are markdown + YAML frontmatter, interface-neutral.

ums/
├── README.md
├── LICENSE
├── skills/
│   ├── ums-init.md       # one-time setup (manual-only)
│   ├── ums-session.md    # orient at session start
│   └── ums-capture.md    # observe, persist, curate
└── template/             # Notion page scaffolds (reference)
    ├── main.md
    ├── subpages.md
    └── task-page.md

Prerequisites: Claude.ai account, Notion + MCP connector, ~15–30 min.

1. Create a Claude.ai project named UMS.
2. Connect Notion MCP — Settings → Connectors → Notion → Authorize. Account-level, works across all projects.
3. Upload the skills — zip the three .md files in skills/ and add via Settings → Skills → +.
4. Run ums-init in a UMS chat. Asks for a parent Notion page (or workspace); creates main page + subpages + Tasks DB; emits the instructions block.
5. Paste the emitted block into Project settings → Custom Instructions. Save.
6. Done. ums-session orients at session start; ums-capture keeps the UMS updated as you work. Both auto-trigger.

MIT — see LICENSE. Copyright (c) 2026 Shivam Thakkar.