Files
reverse-engineering-anything/docs
morluto 6bc74fbc40 feat(evidence)!: require firmware budgets and managed row resolution that producers always write (#11334)
The last fields kept optional "because historical Evidence may omit them"
after Phase 5 (#10510), checked against their producers:

- firmware `analysis_timeout_ms` (inspect_firmware_regions,
  extract_firmware): FirmwareProvider and FirmwarePublication always write
  it, and FirmwareAnalysisService already refused fresh results without it.
  Now required.
- managed call-edge and field-access `target_row_resolved`:
  ManagedMemberRows always writes a boolean. Now required; the comparison
  owner's `undefined` branch and the "historical omission" test are gone.
- Evidence `caller_input_path`: written only when a request selects a
  direct path, so it stays optional; the wording now says that.
- Ghidra `containing_instruction`: optional because other instruction
  statuses have no container; wording corrected.

BREAKING CHANGE: inspect_firmware_regions and extract_firmware results
require `analysis_timeout_ms`, and inspect_managed_members call edges and
field accesses require `target_row_resolved`. Evidence or analysis-view
input without them is refused. Every producer in this release writes them;
recreate observations made by a build that omitted them.
2026-11-16 03:42:04 +08:00
..

Documentation directory

REA documentation is organized by reader task and document owner. This directory links every authored guide; the site also serves separate product pages. The VitePress documentation source is this docs/ tree.

Getting started

Native binaries

JavaScript and Electron

Browser and captured websites

Android applications

Apple applications

.NET assemblies

Firmware

HarmonyOS packages

WebAssembly

EVM contracts

Databases and recorded packets

Process capture and instrumentation

Signal recordings

Provider setup and formats

Contracts and evidence

Development and verification

Release migrations

Architecture and authoring

Machine-owned documentation

Path Owner and update command
public/product-catalog.json Ignored contract projection; npm run docs:generate
verification/managed-conformance-*.json Ignored managed conformance projections; npm run evidence:generate
error-contract.schema.json Tracked schema from contracts; npm run docs:error-schema
user-visible-errors.csv Authored error classification inventory; preserve its schema
releases/<version>.contributions.json Durable release contribution record; follow the release guide
assets/ Shared authored images referenced by guides

Do not edit generated catalogs or evidence to change product facts. Change their canonical contracts or producer and regenerate. Historical release records retain the exact commit messages and references from the release they describe.

Additional guides