NikkiOS Reaches Phase 31

When we started NikkiOS v2, we made a decision that felt radical: write all the documentation first, then the code. Phase -1 was docs only. No exceptions.

Thirty-one phases later, we have a capability-hosting cognitive OS that can read your codebase, search the web, process documents, and even run isolated improvement cycles—all with cryptographic event trails.

What We Built

The architecture held up. Kernel enforces law. Core handles cognition. LLM is a replaceable organ. Tools are peripherals.

Current capabilities include:

• •Multi-model support — Ollama (local), OpenAI, and Anthropic, hot-swappable without restart
• •Document library — Upload, OCR, and index PDFs, DOCX, and text files
• •RAG search — BM25 retrieval over your indexed documents
• •Code tools — File read, directory list, regex search across workspaces
• •Web tools — Fetch pages, Brave Search integration
• •Sandbox execution — Clone repos, run checks, generate patches in isolation
• •Autopilot cycles — Goal-driven improvement loops with candidate builds

What Held

The constitutional constraints from Phase -1 are still intact:

1. •Append-only event truth — If it wasn't logged, it didn't happen
2. •Determinism + replay — Same inputs produce same outputs
3. •Kernel/Core separation — Core proposes, Kernel decides
4. •No capability theatre — Tool calls execute or they don't

These weren't just nice ideas. They've prevented entire categories of bugs and made debugging tractable when things go wrong.

What's Next

Phase 31 isn't the end. We're working on:

• •ToolBridge for remote executors (VS Code integration)
• •Context layer improvements for large workspaces
• •Better artifact streaming for long-running operations

The roadmap is documented in /docs/phases.md. All 20,000+ lines of it.

Try It

NikkiOS runs locally. Windows installer available, or clone the repo and run ./start.bat.

The codebase is the specification. Everything ships with events.