What problem does it solve? Agents entering a repository lack context about system architecture, live services, port mappings, and past decisions, and have no structured way to record work logs or architectural changes back into a persistent knowledge base. ## Core Features & Use Cases - Hybrid Knowledge Search: Combines BM25 full-text search and dense vector embeddings with Reciprocal Rank Fusion to retrieve notes, with optional 1-hop graph context. - Token-Bounded Reading: Extracts machine-actionable boundary contracts (ports, dependencies, invariants) from notes, cutting 70-90% of narrative token bloat. - Blast Radius & Graph Mapping: Recursively maps upstream dependents and downstream dependencies before mutations, with cycle detection. - Structured Mutations & Telemetry: Surgically updates frontmatter keys, appends sections, writes notes, and logs telegraphic work entries under 140 characters. - Use Case: Before modifying a Docker Swarm service, run a blast-radius analysis on the target, read its boundary contract, apply the change, verify wikilink integrity, and log the outcome to the daily ledger. ## Quick Start Ask the agent to search the akatsuki vault for the current project's service topology and port mappings before making any infrastructure changes.