Decide device target admission, recovery, and non-mutation contract

[justsml]

Question

Given the researched device method, what conditions must hold before an owned device enters the program, and what recovery and non-mutation contract governs firmware acquisition, offline analysis, and initial interaction? Decide ownership and authorization evidence, model and firmware identity, backups and restore path, replacement or bricking tolerance, interfaces and isolation, secrets and personal-data handling, vendor disclosure considerations, stop conditions, and the separate approval boundary for flashing, memory writes, signature-bypass validation, or any action with persistent or destructive risk. Do not choose the first device.

[justsml]

Implemented and pushed the evidence-gated device research lane contract in commit 455defb. It separates public research, owned-device offline analysis, non-mutating interaction, and persistent/destructive campaigns; rejects lane or normalized-intent mismatch; requires evidence/isolation/before-after checks; and makes lane 4 depend on a new campaign, rehearsed independent recovery, replaceability, safety planning, disclosure readiness, and operator checkpoints. Eligibility never creates execution authority. Focused integration checks: 7 passing tests across this contract and Target Recipes. Full TypeScript check passes. No device or target interaction occurred. Keeping this HITL decision ticket open.