Skip to main content
Central Mapper generates AST indices and dependency graphs for the Termux Monorepo. It parses source files, extracts function signatures, builds file-level graphs, and records cross-module dependencies so you can navigate the codebase by symbol and relationship rather than by directory tree. The indices live in workspace/llm_map/ and currently cover 8,239 files.

​
Key indices

Central Mapper produces the following indices in workspace/llm_map/:

​
Build scripts and rebuild command

Central Mapper provides three build scripts that you chain together to regenerate all indices:
  • map-build — Scans the repository, parses ASTs, and writes llm_index.jsonl and llm_index_compact.jsonl
  • map-func — Extracts function-level detail and produces func_index.jsonl
  • fore — Runs the forensic pass to build file_graph.json, deps.jsonl, and central_enriched.jsonl
Run the full chain after any significant refactor, merge, or dependency change to keep the indices accurate.
Rebuilding the full index set on a large repository can take several minutes on an Android device. Run it during low-activity periods or in a background Termux session.

​
Directory structure

The workspace/llm_map/ directory is organized as follows:
master_tasks.json is the task registry consumed by the Termux Multi-Agent system. Central Mapper updates task_files_index.json whenever tasks are modified so the agent orchestrator knows which files each task targets.

​
Querying the indices

You can query the indices with standard Unix tools or through ArchWiz forensic modules. For example, to find all functions that reference a specific symbol:
To inspect the dependency graph for a file:
The indices are line-delimited JSON (JSONL) for streaming compatibility. Use jq or rg for fast queries without loading the entire file into memory.

​
Integration with ArchWiz

ArchWiz uses Central Mapper indices for forensic and verification workflows. The correlation_scout.py and fragment_matcher.py tools read file_graph.json and deps.jsonl to find related files and orphaned fragments. When you run oracle <file> from the command line, it consults the dependency index to warn you about downstream impact before you make a change.