AI Flow

Version: adom-aiflow 0.2.56+noah.1 (local build = stock 0.2.56 + hands-on patches), KiCad 10.0.x, hands-off run.

What happened: mid-run the human changed the requirements (the flight controller had to grow from a 32 x 32 to a 64 x 64 large-pin molecule and join the ESC through large needles instead of extra machine pins). I recorded it with adom-aiflow prompt --text ... and amended the load terminals with spec-amend, then built the new board and ran place check --moves.

Error: ERROR: the moved board is not a conforming molecule: fixed reference MC25 missing from current or starting board ... fixed references moved since the run started: MP2 (132.00, 100.00) -> (164.00, 100.00) ... The fixed-reference baseline is the run's start board (run.json board), and nothing re-baselines it, so a human-approved interface change cannot continue in the same run.

What I did: started a second run (intake + start --board on the same prompt time, prompt for the follow-up) and replayed the early steps. That works but splits one job's ledger across two run folders.

Ask: a recorded way to re-baseline the molecule interface after a requirements change from the human, e.g. adom-aiflow requirements change --why "<prompt n>" --board <new board> (or prompt --rebaseline) that keeps the clock and ledger, re-reads fixedRefs from the new board and shows the change on the timeline. A hint on the refusal pointing at it would have saved an hour.