REA artifact investigation
Use the installed REA engine and its matching standalone skill for investigations
of shipped binaries, packages, or requested runtime behavior. For ordinary source
repositories, use source and tests directly. This bridge does not install REA,
Ghidra, a provider, or an MCP server and does not assert they are available.
Use the caller's BACKS Build Flow task packet,
integration owner, and permitted task_mode. A direct investigation establishes
that packet once. bounded-loops owns the deadline and
remaining allowances; provider retries, model changes, and handoffs inherit them.
This is an evidence-producing specialist, not a second adoption or repair owner.
- Resolve the exact target, its identity/hash, the question, and the phase:
discovery of the upstream artifact or verification of a specific native
result. Read the installed upstream
reverse-engineer-anything skill and
relevant references from the host's agent skill directory; avoid
recursively selecting this bridge. If it is unavailable, say so and continue
useful investigation through available tools within the existing budget.
- Use the connected REA tools where available, or the installed REA CLI. For
native binary analysis, use an existing compatible Ghidra provider where
supported; report a missing or unavailable provider rather than inventing a
result or installing dependencies without authorization.
- Start with read-only static inspection. Record target identity, evidence IDs,
scope, limits, and unknowns. Static findings do not prove runtime behavior;
perform live observation only within the user's requested scope and the
declared tool's execution and mutation boundaries.
- Return an evidence packet to the caller: target identity, phase, commands/tool
receipts, evidence IDs, observations, static/runtime distinction, unknowns,
and the remaining mission budget. The caller owns the next step: Absorb applies
its license/dependency gates and native integration; a repair owner applies
root-cause-first and repair-loop. Do not recursively start either lifecycle
from this bridge. If verification finds a defect, return the observation for
a sealed RED and the bounded fix/check loop; do not claim the repair happened.
- Resolve dispatch by role and capability through the configured fleet-ladder;
never hardcode model identifiers. When independent assessment is required,
use the blind-tribunal's fresh author-disjoint execution and author-redacted
packet, subject to capabilities actually provided by the host runtime. A
missing provider or exhausted budget is a checkpoint marked STILL-BUILDING,
with useful observations and the precise next action; it is never fabricated
runtime proof. Keep any unblocked investigation within its remaining allowance.
Scaffold: REA by morluto, MIT license, https://github.com/morluto/rea.
The engine, upstream skill, and providers are separate installations.
1---2name: rea-investigation3description: Use when a shipped executable, package, or requested runtime behavior needs REA investigation for diagnosis, capability discovery, or verification of a native adoption.4license: MIT5metadata:6 source: https://skillmd.com/skills/tcuzzo/rea-investigation7---89# REA artifact investigation1011Use the installed REA engine and its matching standalone skill for investigations12of shipped binaries, packages, or requested runtime behavior. For ordinary source13repositories, use source and tests directly. This bridge does not install REA,14Ghidra, a provider, or an MCP server and does not assert they are available.1516Use the caller's [BACKS Build Flow](../backs-build-flow/SKILL.md) task packet,17integration owner, and permitted `task_mode`. A direct investigation establishes18that packet once. [bounded-loops](../bounded-loops/SKILL.md) owns the deadline and19remaining allowances; provider retries, model changes, and handoffs inherit them.20This is an evidence-producing specialist, not a second adoption or repair owner.21221. Resolve the exact target, its identity/hash, the question, and the phase:23 **discovery** of the upstream artifact or **verification** of a specific native24 result. Read the installed upstream `reverse-engineer-anything` skill and25 relevant references from the host's agent skill directory; avoid26 recursively selecting this bridge. If it is unavailable, say so and continue27 useful investigation through available tools within the existing budget.282. Use the connected REA tools where available, or the installed REA CLI. For29 native binary analysis, use an existing compatible Ghidra provider where30 supported; report a missing or unavailable provider rather than inventing a31 result or installing dependencies without authorization.323. Start with read-only static inspection. Record target identity, evidence IDs,33 scope, limits, and unknowns. Static findings do not prove runtime behavior;34 perform live observation only within the user's requested scope and the35 declared tool's execution and mutation boundaries.364. Return an evidence packet to the caller: target identity, phase, commands/tool37 receipts, evidence IDs, observations, static/runtime distinction, unknowns,38 and the remaining mission budget. The caller owns the next step: Absorb applies39 its license/dependency gates and native integration; a repair owner applies40 root-cause-first and repair-loop. Do not recursively start either lifecycle41 from this bridge. If verification finds a defect, return the observation for42 a sealed RED and the bounded fix/check loop; do not claim the repair happened.435. Resolve dispatch by role and capability through the configured fleet-ladder;44 never hardcode model identifiers. When independent assessment is required,45 use the blind-tribunal's fresh author-disjoint execution and author-redacted46 packet, subject to capabilities actually provided by the host runtime. A47 missing provider or exhausted budget is a checkpoint marked **STILL-BUILDING**,48 with useful observations and the precise next action; it is never fabricated49 runtime proof. Keep any unblocked investigation within its remaining allowance.5051Scaffold: REA by morluto, MIT license, https://github.com/morluto/rea.52The engine, upstream skill, and providers are separate installations.