automatic-cybernetic-flow-design

# Automatic cybernetic flow design ## Contract | Field | Bound contract | |---|---| | Trigger | User wants a cybernetic flow design document specifying sensors, actuators, feedback paths, delays, and oscillation risk for an interactive system. | | Authority | Reversible local: writes only the single named local design document; rollback is deleting or overwriting that file. No remote mutation. | | Side effect | A cybernetic flow design document at the named local path. No source code, runtime, or remote mutation. | | Done | A design document with sections for sensors, actuators, feedback, delay, oscillation, a wiring diagram, and a dynamic-routing note, written to the named local file. | ## Inputs Required: - The interactive system description: what state it controls, what it observes, and what actions it can take. - The primary control objective: the state the system tries to hold or steer. - Observable signals (sensors) and available actions (actuators). - Per-path delay classifications: fixed, variable, or bounded with the bound. - The named local output file path. Optional: - Known latency budgets, stability requirements, existing feedback paths, or constraints on sensors and actuators. - Gain and timing data for oscillation analysis. If absent, the path is marked under-specified. ## Procedure 1. Intake and validate the system description and control objective. Confirm the system is named, the control objective is stated, and the output file path is supplied. Done ...