1.7 KiB
REA roadmap
The platform tracker, process/Hopper tracker, and browser tracker track capability and verification work. Available tools and setup are documented in the investigation guides, installation guide, and generated catalog.
Priorities
- Expand native architecture, type, and indirect-call verification.
- Connect static findings and runtime observations across application layers.
- Improve obfuscated managed-code comparisons and verified native links.
- Extend process, protocol, filesystem, reconnect, and build-comparison coverage.
- Evaluate additional providers and targets when an analyst workflow demonstrates a capability gap.
Admission criteria
New capabilities must return useful evidence through shared CLI/MCP workflows, preserve observations and unknowns, and declare actual authority and lifecycle constraints. Agents compose experiments using ordinary commands, scripts, and fixture servers; custom orchestration needs a demonstrated requirement.
Provider and platform claims require their corresponding real verification lanes. See tool design for choosing a tool boundary and Ghidra semantics for the existing deep-provider contract.
Setup remains additive, reuses existing tools, and requires approval for disclosed configuration and Hopper installation changes. Additional installer choices need an implemented toolchain and explicit scope; setup does not install or upgrade unrelated runtimes or dependencies.