Workbench · Code & architecture
RevEng
Map unfamiliar Python code into file breakdowns, relationships, reports and visible unknowns.
Repository: CinvanaAI/RevEng
Recorded synthetic example. Source with a complete offline example.
See the idea in action.
The static workflow writes a file inventory, relationship map, per-file breakdowns, dossier, validation and unknowns. It does not execute the input repository or call a model.
Three small Python files with explicit imports and function calls.
{
"mode": "Actual static analysis; included synthetic source",
"file_count": 3,
"source_files": [
"formatting.py",
"helper.py",
"main.py"
],
"artifacts": {
"inventory_path": "repo_inventory.json",
"relation_map_path": "relation_map.json",
"file_breakdowns_path": "file_breakdowns.json",
"enriched_path": "enriched_file_breakdowns.json",
"cluster_map_path": "subsystem_map.json",
"flow_map_path": "flow_map.json",
"repo_dossier_path": "repo_dossier.json",
"validation_report_path": "validation_report.json",
"unknowns_path": "unknowns.json"
},
"model_calls": 0
}Try the example.
From the repository root, follow the dependency requirements in the README. This example uses supplied synthetic material.
python -m pip install -e . python -m examples.offline_demo --out output/first-analysis
The static workflow writes a file inventory, relationship map, per-file breakdowns, dossier, validation and unknowns. It does not execute the input repository or call a model.
Complete setup and instructions ↗The interesting part.
Executable source evidence and explicit unknowns make a provisional architecture account auditable.
Where it came from.
Existing public Python repository-analysis application included in the collection.
Current README supplies a complete offline static-analysis entry path plus links to its broader local workbench.
The allowed evidence does not establish its original date or a direct code-parent relationship to Skeleton.