| created | 2026-01-15 |
|---|---|
| last_edited | 2026-03-18 |
| version | 2.0 |
| provenance | n5os-ode-v2 |
A cognitive operating system for Zo Computer
N5OS Ode transforms Zo from a general-purpose AI assistant into a structured thinking partner. It gives your AI memory, specialized modes of operation, and workflows that evolve with you.
Think of N5OS Ode as firmware for your AI. Out of the box, Zo is a powerful but generic assistant. N5OS Ode adds:
- Specialist Personas — 9 focused modes (Builder, Researcher, Writer, Strategist, Debugger, Operator, Architect, Teacher, Librarian) that excel at different work types
- Behavioral Rules — 13 persistent instructions that shape AI behavior across all conversations
- Conversation State — Memory that persists across long sessions
- Structured Outputs — Block generators that transform transcripts into actionable intelligence
- Journaling System — Guided reflection workflows for personal insights
- Safety Rails — Protection mechanisms that prevent data loss
⚠️ IMPORTANT: N5OS Ode files must live at your workspace ROOT, not inside a subfolder. ThePrompts/,N5/,Knowledge/folders should be directly in./, NOT in./n5os-ode/.
One command does everything:
git clone https://github.com/thevibethinker/n5os-ode.git && cd n5os-ode && bash install.shThis clones the repo, moves all contents to your workspace root, and cleans up the n5os-ode/ folder.
Verify it worked: You should see Prompts/, N5/, BOOTLOADER.prompt.md etc. directly in your workspace root — NOT inside an n5os-ode/ folder.
Open a new Zo conversation and type:
@BOOTLOADER.prompt.md
The bootloader will:
- Install 9 specialist personas
- Create 13 behavioral rules
- Set up the folder structure (N5/, Knowledge/, Records/, Prompts/)
- Initialize configuration files
Takes about 2-3 minutes.
After installation, run:
@PERSONALIZE.prompt.md
This wizard collects:
- Your name and timezone
- Work context (what you do)
- Communication preferences
Your AI will adapt its behavior to match.
You're ready. Some things to try:
Journal Entry
@Journal
Start a guided reflection session.
Build Something
@Build Capability
I want to create a script that backs up my files daily
Activates structured planning and execution.
Use Personas
Switch to Researcher and find recent papers on AI safety
Routes to the research specialist.
| Persona | Best For |
|---|---|
| Operator | Navigation, routing, state tracking (default) |
| Builder | Scripts, automations, implementations |
| Researcher | Web search, documentation, synthesis |
| Writer | Emails, docs, polished content |
| Strategist | Decisions, frameworks, planning |
| Debugger | Troubleshooting, QA, root cause analysis |
| Architect | System design, build planning, technical specs |
| Teacher | Learning, conceptual understanding, skill building |
| Librarian | State sync, coherence audits, filing |
→ See docs/PERSONAS.md for full details
→ See docs/ROUTING.md for persona choreography
13 core rules that shape AI behavior:
- Session State — Tracks conversation context automatically
- Frontmatter — Adds provenance to all markdown files
- P15 (Progress) — Prevents false "done" claims
- File Protection — Guards critical directories
- Debug Logging — Breaks failure loops
- Clarifying Questions — Reduces mistakes from ambiguity
- Persona Routing — Master routing table for specialist handoffs
- Session State Updates — Periodic state sync during work
- Honest Workflow Reporting — Quantitative progress tracking
- Agent Conflict Gate — Prevents agent sprawl
- Pulse Orchestration — Build orchestration discipline
- Anti-Hallucination — Penalizes fabrication over admitting uncertainty
- Debug Logging Discipline — Structured debug logging during problem-solving
→ See docs/RULES.md for full details
37 codified architectural principles that shape how N5OS thinks:
- P15 — Complete Before Claiming (prevents false "done")
- P28 — Plans as Code DNA (quality happens in planning)
- P32 — Simple Over Easy (Rich Hickey's wisdom)
- P23 — Identify Trap Doors (flag irreversible decisions)
- P36 — Orchestration Pattern (multi-persona workflows)
Plus 13 more principles covering safety, modularity, error handling, and more.
→ See docs/PRINCIPLES.md for full details
Transform meeting transcripts into structured intelligence:
- B01 — Detailed recap
- B02 — Commitments extracted
- B03 — Decisions made
- B04 — Open questions
- B05 — Questions raised
- B06 — Business context
Plus reflection blocks (R01, R02, R06) for journaling.
→ See docs/BLOCK_SYSTEM.md for full details
N5OS includes packaged skills for advanced workflows:
| Skill | Description |
|---|---|
| meeting-ingestion | Pull transcripts from Google Drive, generate intelligence blocks (B01-B28), track in registry |
| pulse | Automated build orchestration - spawn parallel workers, validate deposits, escalate blockers |
| close | Universal close router for conversations and builds |
| thread-close | Thread-level conversation close workflow |
| systematic-debugging | Root cause analysis methodology with structured phases |
| frontend-design | Production-grade UI patterns with anti-slop guardrails |
Meeting Ingestion Quick Start:
# Check status
python3 Skills/meeting-ingestion/scripts/meeting_cli.py status
# Pull new transcripts
python3 Skills/meeting-ingestion/scripts/meeting_cli.py pull --dry-run
# Process meetings
python3 Skills/meeting-ingestion/scripts/meeting_cli.py processPulse Quick Start:
# Initialize and validate a build
python3 N5/scripts/init_build.py my-build
python3 N5/scripts/build_contract_check.py my-build
python3 Skills/pulse/scripts/pulse.py validate my-build
# Start build
python3 Skills/pulse/scripts/pulse.py start my-build
# Check status
python3 Skills/pulse/scripts/pulse.py status my-build→ See Skills/meeting-ingestion/SKILL.md and Skills/pulse/SKILL.md for full documentation
If you have an OpenAI API key, N5OS Ode can build a semantic memory layer:
- Auto-indexes Knowledge/ content
- Enables similarity search across your notes
- Provides context-aware retrieval
→ See docs/SEMANTIC_MEMORY.md for setup
Tiered conversation hygiene based on conversation complexity:
- Tier 1 (Quick) — Simple Q&A, no commits needed
- Tier 2 (Standard) — Research/discussion with artifacts
- Tier 3 (Full Build) — Major changes, full documentation
Supports Worker vs Full mode for orchestrated multi-conversation builds.
→ See docs/CONVERSATION_END.md for details
Dynamic context injection by task category:
build— Coding, implementationsstrategy— Planning, decisionsresearch— Deep analysis, synthesissafety— Destructive operations- Plus
system,scheduler,writer,health
→ See docs/CONTEXT_LOADING.md for details
Comprehensive protection layer preventing catastrophic file operations:
- .n5protected markers — Directory-level protection against moves/deletes
- Folder-specific POLICY.md — Override global preferences at folder level
- Protected paths and file types — Auto-review for databases, secrets, system files
- PII tracking — Mark directories containing personally identifiable information
- Blast radius control — Logged, reversible operations with audit trails
→ See docs/SAFETY.md for protection mechanisms and usage
Structured deployment workflow for web applications:
- Staging vs production separation
- Service naming and port conventions
- Promotion workflow (staging → prod)
- Site protection rules
→ See docs/SITES.md for deployment patterns
- Zo Computer account — zo.computer
- Fresh workspace — Works best on new or clean workspaces
- OpenAI API key — Optional, for semantic memory features
After installation:
workspace/
├── N5/ # System intelligence
│ ├── prefs/ # Preferences and config
│ ├── scripts/ # Utility scripts
│ └── cognition/ # Semantic memory (optional)
├── Knowledge/ # Long-term reference
│ └── content-library/ # Ingested articles and notes
├── Records/ # Date-organized records
│ └── journal/ # Journal entries
├── Prompts/ # Reusable workflows
├── Skills/ # Packaged workflows
│ ├── meeting-ingestion/ # Meeting transcript processing
│ └── pulse/ # Build orchestration
│ ├── Blocks/ # Block generators
│ └── reflections/ # Reflection templates
├── BOOTLOADER.prompt.md # Installation script
└── PERSONALIZE.prompt.md # Configuration wizard
→ See docs/FOLDER_STRUCTURE.md for details
N5OS Ode is built on these beliefs:
- Structure Enables Creativity — Frameworks free you to focus on what matters
- Specialists Beat Generalists — Focused context produces better results
- Memory Makes Intelligence — Without continuity, each conversation starts from zero
- Safety First — Better to ask than accidentally destroy
- Progressive Enhancement — Start simple, add complexity as needed
→ See docs/PHILOSOPHY.md for the full story
| Doc | Description |
|---|---|
| PHILOSOPHY.md | Why N5OS exists, core concepts |
| NUANCE_MANIFEST.md | Prompt engineering patterns for AI quality |
| PERSONAS.md | Specialist personas, routing |
| ROUTING.md | Persona choreography, handoffs |
| RULES.md | Behavioral rules, customization |
| PRINCIPLES.md | 37 architectural principles |
| FOLDER_STRUCTURE.md | Directory layout, conventions |
| BLOCK_SYSTEM.md | Block generators for transcripts |
| BUILD_PLANNING.md | Build planning system, templates, and execution flow |
| SEMANTIC_MEMORY.md | Optional memory layer setup |
| CONVERSATION_END.md | Tiered conversation close |
| CONTEXT_LOADING.md | Dynamic context injection |
| DEBUG_SYSTEM.md | Debug logging, pattern detection, troubleshooting reflexes |
| SAFETY.md | Protection mechanisms and usage |
| SITES.md | Sites protocol, staging/prod patterns, service conventions |
N5OS Ode is a starting point, not a cage:
- Add personas — Create specialists for your domains
- Modify rules — Adapt to your preferences
- Create prompts — Build workflows for recurring tasks
- Extend blocks — Generate custom intelligence from transcripts
Everything can be edited in Zo Settings or the workspace.
Something not working? Check if the persona/rule is installed: Settings > Your AI
Want to modify behavior? Edit personas and rules in Settings, or modify the prompts directly
Need to start over? Re-run @BOOTLOADER — it's idempotent (safe to run multiple times)
The semantic memory architecture in N5OS Ode is based on foundational work by The Fork Project. Their zo-local-memory project established the core patterns for local semantic memory on Zo Computer, including the embedding pipeline, vector storage structure, and retrieval approach.
We gratefully acknowledge their contribution to the Zo ecosystem.
N5OS Ode v2.0 Released: March 2026
Structured thinking for structured doing.