REA
REA source-code map: setup, routing and artifact analysis
Find the implementation files behind client registration and two different analysis paths
What you will learn
- Start with setup code
- Follow a binary request
- Follow a JavaScript request
Before you start
- A target you own or are authorized to examine
- Node.js and npm
- A selected local provider only if native analysis is needed
Use a harmless artifact to test setup, provenance, limitations and cleanup
Key takeaways
- Setup code and provider routing are distinct.
- JS artifact analysis is a separate path.
- Source inspection is not execution coverage.
Start with setup code
`src/application/Setup.ts` builds and applies selected client changes; `SetupSkill.ts` handles the bundled workflow instructions. Read these beside the installation guide to see which actions require an approved plan.
A README command alone does not show how existing configuration is preserved. The pinned guide documents backups, recovery copies and validation before writes; implementation details may change by release.
Follow a binary request
`SessionProviderRouter.ts` is the useful entry point for provider-bound binary sessions. It should be read with the CLI provider selection and MCP identity contracts rather than assuming a single universal backend.
The Ghidra guide describes its headless session conditions. That path differs from JavaScript artifact inspection and should not be used to explain a JS-only result.
Follow a JavaScript request
`JavaScriptArtifactAnalysis.ts` covers static application artifact analysis. `EvidenceMcpServer.ts` exposes evidence-oriented operations to an MCP client.
These are source-code waypoints, not a claim that all branches were exercised. Pin the commit when filing a behavior report and reproduce on a harmless authorized sample.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Read setup and skill registration together.
- 2
Trace one binary session route.
- 3
Trace one static artifact request into MCP evidence.
Copy-ready example
Setup.ts -> selected client configuration
SessionProviderRouter.ts -> native provider session
JavaScriptArtifactAnalysis.ts -> artifact evidence
EvidenceMcpServer.ts -> MCP responseFrequently asked questions
Where should I look for client setup?
Start with Setup.ts and SetupSkill.ts, then compare with the installation guide.
Where is binary provider routing?
The pinned SessionProviderRouter.ts is the relevant application-layer waypoint.
Sources
- REA / docs/installation.mdSource checked 2026-10-14
- REA / src/application/Setup.tsSource checked 2026-10-14
- REA / src/application/SetupSkill.tsSource checked 2026-10-14
- REA / src/application/binary/SessionProviderRouter.tsSource checked 2026-10-14
- REA / src/application/javascript/JavaScriptArtifactAnalysis.tsSource checked 2026-10-14
- REA / src/server/EvidenceMcpServer.tsSource checked 2026-10-14