Command of the Fold: The Requirements, Stated Before Mechanism

A bubble that forms is not a drive. The author's design says the ship commands the fold: it starts the bubble, stops it, aims it, and it navigates by full coordinates — not only where on the page, but which universe, and what time in that universe. The record holds that control spec and no steering law. This paper states the steering law's requirements, and only its requirements. Nine requirements, R1–R9. Each one states its source: stated by the author, derived from the framework, or set by what the record already shows. Each one also states what would show it to be wrong: the observation or derivation that would defeat the requirement itself. The set splits clean. The destination requirements (R1–R3) say the fold's destination is a full coordinate triple (page, universe, time) set whole, before the drop, with the target's motion in the math. The stop requirements (R4–R5) say the bubble must be stoppable, and the one-way law cuts the word "stop" into three different acts at three different addresses; only two of them are legal. The channel requirements (R6–R7) say command must ride a channel the frame has named (the record names one, electrical, through electrons) and no command may need a signal to cross a severed page. The boundary requirements (R8–R9) say what the set forbids outright and what it does not spend: no steering claim may borrow the torsion channel beyond the support the record gives it, and no requirement in this set quietly assumes the confinement problem is solved. In short: the requirements set stands, judged requirement by requirement in §6. The missing statement this question was waiting for is now supplied. The steering law itself stands exactly where it stood, still owed, and now owed against a written specification.