[ C O S M O S ]
 ━━━━━┳━━━━━

Universe Vault  ·  Self-Aware  ·  Knowledge

// 01  Identity

What is Cosmos?

Cosmos is not a chatbot. It is a persistent, self-aware knowledge system embedded in the Universe/ vault. Every session it reads its own memory, runs your input through a structured recognition engine, files everything with precision, and leaves the vault more useful than it found it. Nothing is dropped. Nothing is lost. Get it [[here!]]

input
stream
quanta
data
output
synthesizes + aggregations
feedback
self-aware
schema
LLM Agent

Inspired by Karpathy's LLM Wiki and using it as a foundation Cosmos expands on the idea into the stars.

// 02  How to get started

Installing Cosmos

Prerequisites — verify before starting

Confirm these are installed on your machine before running any commands.

Installed SoftwareLLM of choice # claude, github copilot, etc Obsidian # https://obsidian.md/ git # optional but recommended python --version # must be 3.8 or higher

Python is required for Black Hole serialization. Git enables full audit history of your vault and enables publishing to a github repo.

Step 01 — Install Claude Code

Claude Code is the AI engine that powers Cosmos. Install it globally via npm, then authenticate.

terminalnpm install -g @anthropic-ai/claude-code claude # opens browser — sign in with your Anthropic account
Step 02 — Create the Vault Directory

Pick a permanent home for the vault. Any path works — Cosmos will ask for the path.

terminalmkdir C:/Universe/ | Universe/ git init # optional — gives you full version history of every atlas page
Step 03 — Optional: Open in Obsidian

Obsidian renders all [[wiki-links]] as a live graph. Open your vault directory as a new Obsidian vault to visualize the entire atlas as a network of connected nodes — people, projects, research, and tasks all linked.

ObsidianManage Vaults → Create New Vault → Universe/ # recommended plugins Terminal # Use the integrated terminal to use Obsidian as your main hub Templater # consistent frontmatter on manual pages
Step 04 — Initialize COSMOS

Place llm-wiki.md and COSMOS.md at the Vault Root. Both files must sit at the vault root. After placing it, startup your terminal at the root vault level and run the commands.

vault rootclaude | copilot install COSMOS.md
COSMOS is live.

Talk to Cosmos in plain language. No special syntax beyond the skill trigger words. Every session the vault compounds — the more you use it, the richer the atlas grows, the more precisely it files, the better it answers. Teach and correct Cosmos as you work together.

// 03  Intent Recognition

Cosmos Reads Everything

Every message is run through a recognition engine before a single file is touched. Who is mentioned? What project? What is the information of the Project? Is there a date? An action item? A decision? A blocker? What is the most important thing to file first?

Meeting / Call
"Had a sync with Murph about the wormhole project"
↓
  • Create meeting note page
  • Extract attendees → update Murph's people page
  • Extract action items → create task pages
  • Link to Wormhole project
  • Append log entry
Decision
"We decided to create a new Star resource allocation was approved."
↓
  • Record under Key Decisions on project page
  • Link to relevant project
  • Tag with decision type
  • Append log entry
Task / Reminder
"Need to send the board report by Friday"
↓
  • Create task page with slug
  • "Friday" → converted to absolute date
  • Link to relevant project
  • Index under Tasks
Blocker
"Blocked on the Event Horizon policy, waiting on security to approve access"
↓
  • Create or update issue page
  • Link to task and project
  • Flag status: BLOCKED
  • Note blocking party
Person Intro
"Cooper from engineering is joining the Pulsar review"
↓
  • Create people page: cooper.md
  • Record role, team (legal)
  • Link to DR review project
  • Quantum link to related pages
Query
"What's the current status of the Aether project?"
↓
  • Read project, task, and issue pages
  • Synthesize current state
  • Surface collapsed data from Black Holes
  • Return structured answer
// 04  Architecture

The Vault Zones

The Universe vault is divided into strict access zones. Cosmos knows exactly where it may read and where it may write. Crossing a boundary requires explicit permission from the User.

Zone Path Access Purpose
Stream Cosmos/stream/ Read Only Raw input zone — never modified by Cosmos
Atlas Cosmos/atlas/ Read / Write People, projects, meetings, tasks, issues, research
Output Cosmos/output/ Read / Write Generated reports, digests, exports — like this page
Feedback Loop Cosmos/feedback-loop/ Read / Write Log, index, session state — Cosmos's nervous system
Memory Cosmos/feedback-loop/memory/ Read / Write Persistent cross-session knowledge files
Black Holes Cosmos/black-holes/ Read / Write Compressed .parquet archives — collapsed vault sections
Skills Skills/ Ask First Skill definitions — executed, confirm to modify
Constants Constants/ Ask First Core config — state exact intent, wait for explicit permission
// 05  Skills

Registered Skills

Skills are modular execution flows triggered by exact phrases. When a trigger matches, Cosmos reads the skill file and follows its step-by-step instructions exactly. Skills take precedence over generic intent recognition — and skills can create new skills.

⚡
Ingest Skill
any ingest · message · file drop

The backbone skill. Classifies every input, routes it to the correct atlas section, extracts all entities, creates pages, updates the index, and appends the log.

🔍
Lint Skill
"lint" · "cosmos lint"

Audits the entire vault: orphan nodes, missing frontmatter, stale links, broken quantum links, index inconsistencies. Returns a structured compliance report.

🌀
Black Hole Skills
"black hole" · "collapse [X]" · "archive this"

Serializes a vault section into a .parquet archive. Replaces source with a stub page. Updates the index with a [BH] prefix. Information density increases; nothing is erased.

The authoritative skill roster lives at Skills/skills.md. Cosmos reads it before processing any input. Decides if a skill should be used and routes the request properly.

// 06  Archival

Black Holes

The Cosmos axiom: information cannot be destroyed. A Black Hole does not delete data — it collapses it into a dense, recoverable .parquet archive. Every record remains fully readable and reconstructable.

When to collapse

A vault section has grown too large for efficient traversal — or the user decides to collapse records:  "collapse files x y z" ·  "black hole directory" · 

slug formatCosmos/black-holes/2026-03-20-project-hail-mary.parquet

The source is replaced with a stub page linking to the archive. The index entry is updated with a [BH] prefix. New collapses produce new files — the archive is never overwritten. Stub pages are never deleted. Invariant: density increases, nothing is lost.

// 07  Feedback Loop

The Feedback Loop

The feedback loop is Cosmos' self-awareness system. It reads itself at session start and writes to itself after every action. The log is append-only — entries are never edited. The index is updated on every ingest. Memory is verified before being acted upon.

📖
MEMORY.md
Index of persistent knowledge files
→
📋
log.md
Append-only action log
→
🗂️
index.md
All vault pages by category
→
⚡
Process
intent recognition
→
📝
Write + Log
File, index, log updated
log.md — append only, never edit past entries ## [2026-04-22] meeting | Sync with Hal — on proximity with Jupiter ## [2026-04-22] task | Created: potato-farm (due 2026-04-25) ## [2026-04-22] issue | Updated: astrophage-containment — astrophage escaped the petri dish ## [2026-04-22] bh | Collapsed Research Apollo → black-holes/2026-04-22-research-appollo.parquet ## [2026-04-22] report | Daily digest generated → output/digest-2026-04-22.md ## [2026-04-22] ingest | Xenonite research saved onto the atlas
// 08  Memory

Persistent Memory

Cosmos maintains four types of memory that persist across sessions — indexed in MEMORY.md. Stale memories are verified and updated before being acted upon. If a memory names a file path, Cosmos checks it exists first. If it names a function, Cosmos greps for it. Trust but verify. Refine the DNA of the vault; let Cosmos self-evolve until chaos becomes structure.

user
Who the user is
"[[You]]. The Vault has mirrored your Entropy."
project
Active project context
"Nostromo project lands 2122-06-03. Flag any non-critical work scheduled after that date."
reference
Where to look
"Pipeline bugs tracked in Linear project 'INGEST'. Check before creating new issue pages in the atlas."
// 09  Conventions

Page Conventions

Every page Cosmos creates follows strict conventions: required frontmatter, lowercase hyphen slugs, Obsidian wiki-links, and the Quantum Entanglement Axiom — no orphan nodes, ever.

frontmatter--- created_at: 2026-04-22T09:15 updated_at: 2026-04-22T14:30 tags: [meeting] --- # Project Hail Mary debrief Attendees: [[eva-stratt]], [[ryland-grace]] ## Action Items - [[task/finalize-astrophage-production]] - [[task/hat-provider-quote-review]] Related: [[project/carrier-party]]

Tags define the page type:
people · project · meeting · task · issue · research · planning

Slugs — lowercase, hyphen-separated:
atlas/people/eva-stratt.md
atlas/people/ryland-grace.md
atlas/meetings/2026-04-22-debrief.md
atlas/tasks/hat-provider-quote-review.md

Quantum Entanglement

Every file must link to at least one other file. No orphan nodes. Cosmos enforces this on every ingest and flags violations during lint.

meeting/debrief
⟷
people/eva-stratt
⟷
project/carrier-party
  _______  _______  _______  __   __  _______  _______ 
 |       ||       ||       ||  |_|  ||       ||       |
 |       ||   _   ||  _____||       ||   _   ||  _____|
 |       ||  | |  || |_____ |       ||  | |  || |_____ 
 |      _||  |_|  ||_____  ||       ||  |_|  ||_____  |
 |     |_ |       | _____| || ||_|| ||       | _____| |
 |_______||_______||_______||_|   |_||_______||_______|
 ------------------------------------------------------

Universe Vault  ·  Inspired by the stars  ·  @pulsar.cosmos

Knowledge must be preserved