21 lines
1.5 KiB
Markdown
21 lines
1.5 KiB
Markdown
# Active phase: reverse engineering
|
|
|
|
User confirmed restart and asked for an explicit framework-to-RE transition. Framework is done;
|
|
active work is `research-completion-abi`, recovering actual original record construction and
|
|
ownership required by the research write-back pilot. No general orchestration expansion.
|
|
|
|
Normal loop lead and analyst: GPT-5.6 Sol through the existing bounded launcher. GPT-6 Astra is
|
|
reserved for problem/surprise resolution. Canonical
|
|
repositories remain at RE 3bfde5a / engine 7741d42 plus reviewed uncommitted rollout source.
|
|
Config loader/model check and campaign validation passed after restart. No open surprises.
|
|
|
|
Scope split: analyst recovers ObservedTech/event allocation/string/container ABI from fresh
|
|
read-only original-binary evidence. Lead checks completion effects and helper boundaries.
|
|
Raw captures go to verify/results/research-completion-abi; decisions/handoff to campaign/research.
|
|
No Windows/Ghidra mutation or replacement deployment under this analysis contract.
|
|
|
|
Lead checkpoint: fresh OnTechResearched and UpdateNodeBoreParams decompilations/disassembly
|
|
captured under verify/results/research-callback. Original executable SHA matches fingerprint.
|
|
Callback order and W1 numeric path confirmed from instructions. Ghidra's non-returning delete
|
|
annotation demonstrably truncates pointer clearing/returns; affected lifetime claims require
|
|
instruction-stream evidence. Details: research-callback-order.md. Analyst owns separate record ABI.
|