init vs build
Two steps, one setup. init takes 15 seconds. build takes one conversation.
npx ideaverse-os initScaffolds the folder skeleton and writes every lean file with [TODO] placeholders. No questions. No LLM needed. Just Node 20+.
Output
29 files, 9 folders, under 15 seconds.
/ideaverse-os buildA 5-phase interview. The LLM asks, you answer, it compiles. Each phase writes one or two lean files. Skip nothing on the first run. Re-run any phase to refresh it later.
Output
6 lean files with your actual content. No more placeholders.
The skeleton
init is deterministic and non-destructive. If a target file already exists, it prompts per-conflict: overwrite, skip, diff, or abort. The skeleton is the same for every user -- build is where it becomes yours.
| Path | Purpose |
|---|---|
00-agentic-OS/ | Lean files with [TODO] placeholders |
10-cortex/ | Cortex (knowledge articles) root |
40-raw/ | Ingestion: web clips, youtube, papers |
50-research-library/ | Curated research staging area |
60-skills/ | Bundled skills: build, capture, cortex |
70-daily/ | Daily notes |
80-visualization/ | Attachments and diagrams |
99-archive/ | Compiled raw sources |
CLAUDE.md | Claude Code convention file |
GEMINI.md | Gemini CLI convention file |
AGENTS.md | Codex / OpenAI Assistants convention file |
.cursorrules | Cursor convention file |
.gitignore | Privacy-first defaults |
One question at a time
Run all five in order: /ideaverse-os build. Or run any phase independently: /ideaverse-os build --phase=compass. Each phase follows the lock-file flow: compile to a lock, review, confirm, promote.
What you are optimizing for. This week, this month, this quarter. Success metrics. Collision rules when priorities conflict.
compass.mdWho you are when you sit down to work. Drives, first principles, roles, working style, behavioral rules for every session.
me.md + soul.mdHow you actually work day to day. Which LLM tools you use, your stack, file naming conventions, and daily rhythm.
user.mdHow your vault splits across your two main domains. Pick from 6 starter templates or go custom.
20- and 30- domain foldersOpt-in power-ups: Claude session hooks, GitHub private backup, WSL path configuration. All independent, all skippable.
runbook.md, paths.jsonNothing writes without your sign-off
Every phase compiles into a .lock.md file first. You review the proposed content, then confirm. Only on confirmation does the lean file get written. The lock file is deleted on success and kept on abort -- so mid-flight sessions are resumable.
1. Q&A -- LLM asks one question per turn 2. Compile -- answers -> proposed content 3. Lock -- writes 00-agentic-OS/<file>.md.lock.md 4. Confirm -- show summary, ask [y]es / [n]o / [d]iff 5. Promote -- copy lock -> <file>.md, delete lock Reject -- revise the affected section, rewrite lock, re-ask
Re-running a phase on an already-compiled file triggers a merge flow: the LLM shows what changed and lets you update specific sections rather than starting from scratch.
One command to scaffold. One conversation to personalize.
$ npx ideaverse-os init ~/my-vault # then open ~/my-vault in Claude Code, Cursor, Codex CLI, or Gemini CLI and run: /ideaverse-os build