REA documents native programs, managed code, Android packages and devices, web and Electron applications, firmware and other artifacts. Support is operation-specific: identifying file metadata differs from decompiling a function or observing runtime behavior. Choose the target and exact question first, then check the provider requirement and installed release rather than treating the broad list as a universal capability guarantee.
Choose an evidence operation
Ask whether you need a header field, function body, resource, network exchange or controlled process trace. Each has different prerequisites and evidence strength. The official README and installation guide are the primary sources for the current target table.
Record the boundary
Save the artifact hash or URL, REA release, provider, selected component and any tool limitation. A static path can explain possible behavior, while a runtime trace covers only the observed scenario. If a provider is missing, mark the operation unavailable in that environment.
Requirements & evidence
- Resource type
- Guide
- Category
- Unknown
- Host platforms
- Unknown
- Targets
- native, android, dotnet, electron, web, firmware
- Level
- Intermediate
- Source checked
- 2026-11-03T04:27:22.131388+00:00
Primary sources
- https://raw.githubusercontent.com/morluto/rea/main/README.md
- https://raw.githubusercontent.com/morluto/rea/main/docs/installation.md
Source descriptions establish documented scope. They do not establish that every workflow has been reproduced by AI Craft Pad.