rea/docs

Documentation directory

REA documentation is organized by reader task and document owner. This directory links every authored guide; the site also serves separate product pages. The VitePress documentation source is this docs/ tree.

Getting started

• Installation and setup
• Client configuration and troubleshooting
• CLI and Evidence
• Guided MCP prompts and completion

Native binaries

• Native binary investigation
• Go binary build metadata
• Offline binary diagnostics
• Recorded crash evidence

JavaScript and Electron

• JavaScript Application Graph
• Cross-layer JavaScript application workflows
• JavaScript artifact reconstruction
• JavaScript source recovery
• Passive Node and Electron runtime observation
• JavaScript static/runtime reconciliation
• Electron file-page observation

Browser and captured websites

• Website observation with CDP
• Browser scenario contract
• Website runtime source attribution
• Historical web network captures
• Captured website source locations
• Captured website module relationships
• Captured website scripts and static JavaScript analysis

Android applications

• Static Android APK analysis
• Apktool resource decoding
• ADB device inspection and acquisition
• Flutter build identification

Apple applications

• Apple Application Inventory Projection

.NET assemblies

• Managed-code analysis

Firmware

• Firmware analysis

HarmonyOS packages

• Static HarmonyOS package inventory

WebAssembly

• Offline WebAssembly artifacts

EVM contracts

• Offline EVM bytecode

Databases and recorded packets

• SQLite database snapshots
• Recorded packet capture inspection
• Packet capture summaries

Process capture and instrumentation

• Process capture
• Frida instrumentation

Signal recordings

• Recorded signal inspection

Provider setup and formats

• Ghidra provider semantics
• DOS MZ and COM analysis with Ghidra
• Optional NativeAOT metadata recovery
• MIPS ELF analysis through Ghidra
• PSP static ELF analysis through Ghidra
• RISC-V ELF analysis through Ghidra
• Windows Ghidra P0
• Headerless raw-binary analysis with Ghidra
• IDA provider
• JEB instrumentation and analysis

Contracts and evidence

• MCP runtime contracts
• Reconstruction obligation ledgers

Development and verification

• MCP tool design
• Testing REA
• Client and agent verification
• Reconstruction readiness conformance
• Releasing REA
• REA roadmap

Release migrations

• Upgrading from REA 6.1 to 6.2

Architecture and authoring

• Architecture map
• Documentation ownership and contribution model
• Feature specifications
• Architectural decision records

Machine-owned documentation

Path	Owner and update command
public/product-catalog.json	Ignored contract projection; npm run docs:generate
verification/managed-conformance-*.json	Ignored managed conformance projections; npm run evidence:generate
error-contract.schema.json	Tracked schema from contracts; npm run docs:error-schema
user-visible-errors.csv	Authored error classification inventory; preserve its schema
releases/<version>.contributions.json	Durable release contribution record; follow the release guide
assets/	Shared authored images referenced by guides

Do not edit generated catalogs or evidence to change product facts. Change their canonical contracts or producer and regenerate. Historical release records retain the exact commit messages and references from the release they describe.