Persistent memory
A PARA wiki stores evidence, verified facts, project state, and owner policy in plain markdown. Retrieval checks provenance before it answers.
L0 · L1 · L2 · L3Claude Code × Codex × Obsidian
Give AI a memory that compounds.
Plain-text knowledge, trust-aware L0-L3 retrieval, isolated work, personal, and client zones, plus guarded work-only evolution.
Local-first. Your notes stay plain-text files on your machine.
vault · graph
Claude Code
+
Obsidian
Every session starts smarter than the last.
AI tools do not reliably carry project context from one session to the next. Vault OS gives Claude Code and Codex a shared, plain-text knowledge base for projects, decisions, and sources. Return later and the evidence is still there, with provenance and trust intact.
What you get
Memory with an explicit trust model.
Not a prompt pack. An empty Obsidian template plus a local runtime for Claude Code, with optional Codex integration.
Isolated zones
Work, personal, and client zones never mix. Each keeps its own index, log, and memory. Switch the whole session with one sentence.
work · personal · clientCurated skills & integrations
150 bundled skills and 29 optional Claude plugin entries cover design, development, research, review, marketing, and media work.
plugins · skills · toolsAutomation hooks
Lifecycle hooks register turns and zone switches. Shared locks and local Git authority receipts keep retrieval consistent.
register · lock · verifyIt improves itself
An evolution loop tidies the vault, refreshes retrieval, and learns from completed work turns inside an owner-approved policy.
select · verify · checkpointLocal-first & private
Plain files on your machine, versioned with local Git. The template ships no notes, accounts, tokens, traces, or private paths.
plain-text · local git
Add-ons
Add Codex as a second vault-aware work partner, or ECC as a project-scoped development framework. Both integrations are optional.
How it works
A brain, a pair of hands, and a loop between them.
Obsidian holds the knowledge. Claude Code and Codex do the work. An evolution loop keeps the whole thing tuned.
You ask.
the hands act
the brain records
the loop refines
the next ask starts smarter.
Automation · hooks
It works while you work.
Three lifecycle events maintain a recoverable session trail. They check health, register each turn, and close it cleanly for later reflection.
session start
SessionStart
Checks system health and reports a repair or evolution nudge when attention is due.
before each turn
UserPromptSubmit
Registers the turn so its zone, lifecycle, and later disposition remain traceable.
after each response
Stop
Finalizes a recoverable trace that guarded, work-only reflection can inspect later.
bounded
Hooks track lifecycle state. Durable vault edits still use explicit locks, validation, and local Git checkpoints.
Stays sharp · evolution
It keeps itself sharp.
A loop tidies the vault, learns from completed work turns, and updates retrieval. One explicit owner policy defines what may proceed and what must stop.
owner policy → verifier → local checkpoint
- 1
Detect. The Curator and reflection selector inspect the wiki and structurally completed work turns.
- 2
Propose. New memory is limited to evidence, verified facts, and project-level synthesis.
- 3
Verify. Exact evidence, zone, provenance, code identity, and scope checks fail closed.
- 4
Checkpoint. Accepted changes and small authority receipts are committed to local Git.
Curator keeps it clean
On a cadence, it reviews memory and the wiki, then consolidates and re-syncs the index.
Orphans3 foundlinked
Stale notes5 foundrefreshed
Duplicates2 foundmerged
Overgrown logs1 foundfolded
Indexdriftre-synced
L3 never self-approves. Destructive, privacy, credential, verifier, and zone-policy changes require a live owner decision.
Reflection learns from friction
It reads session history for the rough spots and proposes a fix for each.
session history
friction spotted
fix proposed
Catches where you corrected it or repeated yourself — then suggests a change.
It grows new skills
Repeat a procedure and it offers to capsule it into a reusable skill.
repeat ×3
propose draft
you approve
reusable skill
double filter — Claude's judgement, then yours — keeps the set clean; capsules update on drift
Install
Ask once. Review every trust choice.
Open Claude Code and ask it to install the repository. The guided flow creates a new vault and preserves your existing settings.
01
Open Claude Code
Start on macOS or Linux with Git and Python 3 available. Windows users can use WSL for the full runtime.
02
Say the word
Ask it to install the repo. Answer the short setup and L3 trust quiz, then choose a new or empty vault path.
✓
That’s it
The installation workflow validates all three zones, commits local authority receipts, and proves retrieval before reporting success.
> install github.com/mrDesign-ww/vault-os
reading shell · found 29 plugin entries, 150 skills
? What should the system call you? Example Owner
? Language for the vault? English
? Approve the bundled L3 doctrine? yes
✓ empty vault · plugins · skills · contracts
✓ three indexes validated · trust chain bound
done. your vault is live
What’s inside
The whole kit, in one manifest.
The vault and its memory indexes stay local. Optional connected plugins follow their own privacy policies.
vault-os.manifest
---
plugins: 29 # optional Claude plugin entries
skills: 150 # design, dev, review, research
contracts: Claude Code · Codex # vault-native behavior
zones: work · personal · client # fully isolated
memory: PARA · L0-L3 · role loadouts · Git authority
evolution: guarded reflection # work-only, L3 excluded
hooks: session-aware · zone-aware # crash-safe lifecycle
add_ons: Codex · ECC # optional engines
storage: plain text · local Git # local-first
license: MIT
---