Files
rea/skills/reverse-engineer-anything/references/evidence-workflows.md
T

1.7 KiB

Evidence, comparison, and verification workflows

REA results are Evidence v2. Cite evidence IDs and preserve authority, limitations, coverage, and residual unknowns. Read the smallest deterministic page that answers the question. Continue from a returned next offset while has_more is true only when exhaustive coverage matters.

Use record_unknown only with explicit approval and name the authority or environment still required. Supply supporting and contradicting evidence IDs. Use update_unknown with the current revision; reread after a stale revision instead of retrying blindly. Only qualifying observed evidence can verify a resolution.

Use comparisons with complete, compatible page sets when claiming equivalence or absence:

  • compare_artifacts compares inventory pages by occurrence path, content, metadata, and graph relations.
  • compare_functions compares explicit function Evidence, not fuzzy whole-binary matches.
  • compare_bundles compares canonical bundle membership and unknown history.
  • find_changed_behavior combines existing comparisons; static differences remain candidates, not causal proof.
  • build_call_path needs explicit function dossiers from one artifact/provider; an incomplete frontier makes absence unknown.
  • correlate_static_and_runtime uses explicit mappings; matching patterns are hypotheses, not causality.
  • verify_reconstruction evaluates a finite typed specification. A pass covers only declared comparable claims, not global equivalence.

Process captures are opt-in behavioral evidence, not a security sandbox. V3 captures cannot be upgraded to V4; rerun the original scenario. Distinguish root exit from descendant settlement and require freshness when the task needs it.