docs: organize canonical documentation layout (URGENTE)
Group all existing authored guides by domain and ownership, expose complete navigation, and preserve their public routes. Update physical path consumers and release configuration while retaining historical records. Document domain-based specs and ADR slugs without global numbering. Co-Authored-By: Codex <noreply@openai.com>
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
# REA roadmap
|
||||
|
||||
The [platform tracker](https://github.com/morluto/rea/issues/32),
|
||||
[process/Hopper tracker](https://github.com/morluto/rea/issues/48), and
|
||||
[browser tracker](https://github.com/morluto/rea/issues/39) track capability and
|
||||
verification work. Available tools and setup are documented in the
|
||||
[investigation guides](https://rea.tools/guides/),
|
||||
[installation guide](../getting-started/installation.md), and
|
||||
[generated catalog](../reference/mcp-contracts.md#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](testing.md#real-toolchain-verification-lanes).
|
||||
See [tool design](tool-design.md) for choosing a tool boundary and
|
||||
[Ghidra semantics](../providers/ghidra-provider.md) 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.
|
||||
Reference in New Issue
Block a user