Nautilus is a local-first autonomous environment for personal knowledge management, multi-dimensional semantic indexing, and secure AI agent orchestration. It is built upon the SOVRN Architecture blueprints—a set of sovereignty-first, zero-telemetry, and highly resilient technical principles.
Nautilus is divided into modular directory boundaries:
/apps/knowledge-graph(Nooscope UI): A WebGL-powered 3D force-directed node visualization dashboard (Next.js 16 + React + Three.js). Features custom GraphRAG searches and supports a robust offline fallback (walkVault) sweeping local Obsidian directories when database servers are offline./core/enerv(ENERV Indexer): A fast, schema-first environmental compass (Python CLI). Validates project directories against strict JSON contracts (.facets/meta.json) and powers the localfacet ingestpipeline./config(Shared Service Configs): Houses LiteLLM provider configurations and holds the dynamic service registry updated by the Port Broker./scripts(Lifecycle & Port Broker Automation): Prevents port collisions on local Windows hosts via socket availability sweeps, automatically synchronizing dynamic ports across envs (.env,.env.local,.hermes/config.yaml).C:\telo\Efforts\Simmering: The back-burner zone for active ideas fermentation./hermes/skills(Orchestration & Skills): The central AI pilot gateway. Listens to Telegram bot directives, manages cumulative dry-runs, and dispatches tasks to specialist coding agents (Aider, Cline). Includes the Resonance Audit skill for cognitive bandwidth management./Atlas/Maps/Interests MOC.md: The central index for high-resonance "Drive" projects.
Nautilus enforces a Zero-Clutter Root Policy to minimize "Folder Tax" and maximize focus. For a canonical Solo Vibe Coder setup:
- ACE Core: The project root (
C:\telo) must only contain the three ACE pillars (Atlas, Calendar, Efforts), essential logs, and minimal system configs (.env,.mcp.json). - Agent Redirection: All agent-specific working files (keche, configs, persistent state) must be relocated to a centralized
C:\agents\<AgentName>directory and mapped back via hidden Symbolic Junctions. - STIER Dimension: Efforts should be tagged with ⚡ Drive or 🛠️ Duty prefixes to enable the Resonance Audit and maintain energy balance.
- Autonomy Under Failure: The stack is designed to operate 100% offline on your local hardware (Surface Studio/WSL2) if every cloud goes dark. Local GGUF (
llama-server) and local Obsidian directories serve as the guaranteed baseline floor. - Zero Telemetry Constraint: Opaque development environments with closed telemetry tracking are strictly prohibited. Open, local-first tools (Zed, Aider, Cline) are leveraged exclusively.
- Gateway Agnosticism: All Large Language Models are routed through a central LiteLLM gateway (
localhost:4000) with dynamic failover arrays (Free cloud pools first → Local GGUF second → Paid cloud third).
Initialize the environment configuration by copying the template and setting up your keys:
cp .env.example .envExecute the canonical launch script. The Port Broker will scan for available host ports, synchronize configurations, and safely start all database, inference, and visualization services:
./scripts/master-restart.ps1The Python-powered facet CLI provides a unified control interface:
- Ingest Documents: Chunk, hash, embed, and transactionally merge files into your knowledge graph with automatic metadata inheritance:
facet ingest path/to/note.md
- Audit Directory Contexts: Recursively scan all project directories for schema drift or missing configurations:
facet audit
- Open 3D Visualization: Instantly map the current directory context in the WebGL Nooscope UI:
facet visualize .
Echo — the local-first dictation app — can drop voice notes straight into the mesh. Echo is the sensory audio bridge: you speak, and your words become a note Nautilus ingests.
In Echo's Settings → Advanced, set the Voice capture folder to a Nautilus/Obsidian inbox directory and add a trigger phrase (e.g. запиши в наутилус). Saying "<phrase> …" writes a timestamped markdown note (with source: echo frontmatter) into that folder instead of typing it into the active app. The normal facet ingest / n8n pipeline then consumes it — no extra wiring, fully local and sovereign.
The full system architecture, bitemporal memory designs, and multi-phase rollout lifecycles are documented in the Nautilus White Paper:
- Vision & Principles: Failure boundaries and zero-telemetry rules.
- Architecture Overview: Metadata, semantic, and orchestration layers.
- Core Components: Monorepo folder layouts and dynamics.
- ENERV: Metadata Mesh: Schema-first faceted directory indexer.
- Knowledge Graph & RAG: Ingestion flows, 3D WebGL, and
walkVaultlocal fallbacks. - Technical Stack: LiteLLM rotating pools and SecOps Sovereign Shield monitoring.
- Phased Roadmap: Progression timeline (Phases 0 to 4).