reverse-engineer-rpi

Reverse-engineer a product into a mechanically verifiable feature inventory + registry + spec set, with optional security-audit artifacts and validation gates. If you do not have explicit written authorization to analyze that binary, do not run the above. Use the included demo fixture instead (see Self-Test below). Repo-only example (no binary required): Pinned clone (reproducible): Required: Optional: Security audit flags (optional): Mandatory guardrail flag: Use --upstream-ref to pin a repo-mode clone to a specific commit, tag, or branch. This makes analysis reproducible and allows golden fixtures to be diffed against a known baseline. When --upstream-ref is provided: clone-metadata.json schema: Repo-mode analysis writes machine-checkable contract files under output_dir/ . These files use only relative paths, sorted lists, and stable keys — no absolute paths, no run-specific timestamps — so they can be committed as golden fixtures and diffed across runs. Primary contract files: Example feature-registry.yaml structure: Note: Contract outputs are written by --mode=repo (or --mode=both ).