REA can inspect a local JavaScript directory or Electron ASAR without executing application code and project packages, bundles, windows, preload boundaries and selected IPC facts into an evidence-backed application graph. Start with one authorized artifact, preserve its hash and coverage report, and treat inferred relationships as navigation aids until a separate static or runtime observation confirms them.
Build the static map
Analyze the selected directory or ASAR and inspect the returned coverage and limitations before following routes, windows or IPC relationships. Keep source locations and artifact identities beside every important claim. Missing source maps or dynamic construction can leave parts of the application unresolved.
Add runtime evidence only when needed
A static graph does not prove which code executed. If the question requires runtime attribution, capture a separate authorized browser, Electron or V8 observation and reconcile the records. Preserve unknown relationships instead of converting plausible matches into confirmed behavior.
Requirements & evidence
- Resource type
- Guide
- Category
- Unknown
- Host platforms
- Unknown
- Targets
- electron, web
- Level
- Advanced
- Source checked
- 2026-11-04T05:16:02.087600+00:00
Primary sources
Source descriptions establish documented scope. They do not establish that every workflow has been reproduced by AI Craft Pad.