Zero-token knowledge base
Architecture maps, an overview video, and the full documentation set, generated offline from the source code. Nothing here was written by an LLM.
Physics-driven diagrams: drag nodes, click one for its documentation, trace upstream or downstream reach. Maps load their engine from a CDN.
Tiered architecture (upward dependencies that break the layering in red) plus, for every entry point, a control-flow chart, the call tree in real call order and the cross-file sequence. Zoomable, every box opens its signature and docs.
Every file, community, layer and external in 2D or 3D: clickable nodes and edges, upstream and downstream reach, path finder, color by community, layer or language, and lenses for import cycles, files nothing imports, and hubs.
Hierarchical edge bundling on a circle or a 3D sphere of community caps: every import routed through its community, thick bundles mark the seams between subsystems, live bundling strength, crossing-only filter.
Component architecture map: layered left-to-right diagram with labeled relations, hover descriptions, click-to-component, sub-component expansion, and the analysis.json with method-level call evidence. No LLM needed.
Components, services, storage, and boundaries across layers.
Movement of data from sources through transforms to stores.
States, transitions, waits, and retry paths of change.
Ordered interaction between top participants over time.
Delivery path across lanes from entry to terminal outcomes.
Concept pages per code community: start with index.md.
readmenator-wiki/index.md
The codebase centres on lazyowninfinitestorage.py, testsecurity.py, testintegration.py. Architecturally it is 3 layers, dominant testing (6 files) across 2...
readmenator-wiki/community_0_root.md
Community 0 | 10 files | cohesion 1.00
readmenator-wiki/community_1_orphans.md
Community 1 | 1 files | cohesion 0.00
readmenator-wiki/concepts.md
Second-brain semantic layer: nouns map atomically to file sets (EXTRACTED); verbs aggregate structural edges (INFERRED).
readmenator-wiki/queries.md
Log each answered question here so the wiki compounds. Format: question, answer, cited files.
readmenator-wiki/REPORT.md
Project: LazyOwnInfiniteStorage | 2026-10-17 | offline, deterministic
Community report hierarchy for agents. Query it with: readmenator . ask "question" (or MCP readmenator.graphrag).
readmenator-graphrag/REPORTS.md
Entities: 287 | Relationships: 748 | Communities: 2 | Themes: 0 | Text units: 205
Knowledge base, README, and policies.
KNOWLEDGE_BASE.md
Start here: Statistics Dashboard for scope, God Nodes for blast radius, Architecture Reference for per-file API. Agents: prefer readmenator-agent/INDEX.md +...
README.md
Production-grade tool for encoding any file into a video and decoding it back with full data recovery, even after video resolution changes.
readmenator-diagrams/overview.md
Static architecture map of 11 files (py, sh) in 1 components: root. Structure is extracted statically without LLM calls; component prose may be enriched...
readmenator-diagrams/root.md
root groups 10 files (py) around LazyOwnConfig, SecurityValidator, init, validatefilepath, validatesize. LazyOwnInfiniteStorage - Production-grade...
SECURITY.md
Use this section to tell people about which versions of your project are
Grep-friendly indexes for AI agents (also useful for humans).
readmenator-agent/INDEX.md
readmenator-agent/API.md
Imported by: mcpserver.py, skilllazyowninfinitestorage/tools.py, tests/testerrorcorrection.py, tests/testframes.py, tests/testintegration.py...
readmenator-agent/ARCHITECTURE.md
mcpserver.py -> lazyowninfinitestorage.py
readmenator-agent/CONCEPTS.md
Nouns map atomically to file sets (EXTRACTED); verbs aggregate structural edges (INFERRED).
readmenator-agent/GOTCHAS.md
These files have the most connections. Changes here have high blast radius.
readmenator-agent/KB_misc.md
Doc: MCP tools for LazyOwnInfiniteStorage integration.
readmenator-agent/KB_root.md
Doc: Verificar si Python está instalado
readmenator-agent/KB_tests.md
Doc: Unit tests for ErrorCorrector Hamming(8,4) implementation.
readmenator-agent/MEMORY.md
Generated from 11 files at commit d4b6ed81f514. Read this first, then readmenator-wiki/index.md, then readmenator . ask "<question>" for anything specific.
readmenator-agent/SECURITY.md
readmenator-agent/SYMBOLS.md
Step-by-step tasks grounded in this codebase.
readmenator-agent/recipes/add-function.md
Find the target file by purpose: grep -in '<topic>' readmenator-agent/INDEX.md
readmenator-agent/recipes/change-impact.md
Riskiest file: lazyowninfinitestorage.py (9 dependents)
readmenator-agent/recipes/fix-cycle.md
Read cycles: grep -A5 'Dependency Cycles' readmenator-agent/GOTCHAS.md
readmenator-agent/recipes/fix-security.md
Read findings: grep -n '<file>' readmenator-agent/SECURITY.md
readmenator-agent/recipes/reduce-complexity.md
Target hotspot: lazyowninfinitestorage.py
Open any map, then: drag nodes freely while physics settles the rest, search (/) to filter, click a node to focus it with full file documentation, Upstream and Downstream to trace authored reach, Path to probe the exact route between two ids, Lens to compare semantic roles, Play to walk the guided chapters, Stabilize to re-run physics, Theme for dark and light, Export for PNG or typed JSON. Deep links such as #route=a~b restore any reading.