Architecture and dependencies
Source areas, manifests, configuration, APIs, infrastructure, deployment files, dependency edges, and recovery signals.
Project Brain
Statically scan a Git repository or any ordinary local project folder into one focused .rrbrain SQLite file—without executing the project’s code.
Connected evidence
Project Brain records where evidence came from and how project elements connect, so a person or agent can ask a focused question instead of ingesting the entire tree.
Source areas, manifests, configuration, APIs, infrastructure, deployment files, dependency edges, and recovery signals.
Local test evidence plus bounded imports such as SARIF, JUnit, coverage, OpenAPI, SBOM, Terraform, and Compose fragments.
Decisions, failed attempts, active findings, recovery knowledge, snapshots, diffs, and change-impact traversal.
First local snapshot
The scan is bounded and static. The generated visualization is a self-contained local HTML file with no remote scripts, fonts, analytics, or requests.
rehearse brain build . --output project.rrbrain --label initial
rehearse brain summary project.rrbrain --json
rehearse brain query project.rrbrain "database recovery" --json
rehearse brain visualize project.rrbrain --output project-brain.html
Offline visual
Explore nodes and evidence connections without a hosted graph service.
Compare structural snapshots and inspect added, changed, or removed evidence.
Review detected gaps with confidence and a route to verify each one.
Bring recovery-related artifacts and missing evidence into one view.
Keep imported and scanner-derived evidence distinguishable by provenance.
Follow snapshots, decisions, failures, and project memories over time.
Privacy boundary
A brain can contain sensitive project metadata. Keep *.rrbrain out of version control and review ignore rules before scanning. .rehearseignore controls what the scanner reads; it is not a Git privacy boundary.
Evidence, not authority
Findings point to missing or conflicting evidence and provide a verification route. They are not automatic legal, privacy, accessibility, security, or architecture conclusions.