[Intro — Diagnostic Voice] INPUT: GREEN. OUTPUT: WRONG. INTERFACE: CLEAN. WHO TOUCHED THE MODULE? Read the maintenance specifications. [Verse 1] You wanna read the wires all night, trace every bit from left to right, follow the pipe into the wall, memorize the system call. But pressure’s good at point A, pressure’s dead at point B, cut the coupler, swap the line— why dissect the whole machine? [Pre-Chorus] Don’t worship implementation, check the contract, check the state. If the boundary does its function, why romanticize the trace? [Chorus] Read the maintenance specifications! Input, output, isolation! Cut the line at the connection, swap the broken implementation! Read the maintenance specifications! Test the rule, not your narration! If the module meets the contract, I don’t need your meditation! [8-bit Brass Break] Ba-da! Ba-da! BEEP—BEEP—CLACK! Ba-da! Ba-da! ROLL IT BACK! [Verse 2] “This function here—what does it do?” Depends how far you want me through. Cache and queue and foreign state, three old jobs that execute late. You know these twenty lines by heart? Great—now tell me every part that breaks when one return gets changed through seven services rearranged. [Pre-Chorus 2] Reading isn’t verification. Knowing syntax isn’t proof. Show me failure containment. Show me what remains unmoved. [Chorus] Read the maintenance specifications! Input, output, isolation! Separate the responsibilities, build for replacement, not devotion! Read the maintenance specifications! Guard the invariant relation! If the output stays deterministic, ship the new implementation! [Dub Breakdown — Half Time] Clean water in. Clean water out. If the middle turns it brown— disconnect. No pilgrimage through every hose. Replace the section. Run the test. [Glitch Build] SPEC! BOUNDARY! CONTRACT! TEST! SPEC! BOUNDARY! CONTRACT! TEST! [Bridge — Robotic Call & Response] What is correct? —DEFINED BEHAVIOR! What may change? —IMPLEMENTATION! What must remain? —THE CONTRACT! What do we test? —OBSERVATION! Who reads every single line? … [Tiny 8-bit Silence] Exactly. [Final Chorus] Read the maintenance specifications! Not the code as holy scripture! Split the system into pieces, make the failure small and visible! Read the maintenance specifications! Rules before interpretation! Understand the specification— then replace the implementation! [Outro — Arcade Shutdown] INPUT: VERIFIED. OUTPUT: VERIFIED. REGRESSION: PASS. Internal details? Not required.
