01: The Impedance Mismatch
Legacy Gravity vs. AI Thrust
We are attempting to attach a rocket engine (Agentic AI) to a wooden cart (Legacy "Hard" Architecture). The friction generated by this attempt is what we call the Translation Tax.
The Villain: Book.php
Consider a typical legacy artifact: a 1,500-line book() method taking 18 parameters, entangled with raw SQL, global singletons, and buried business lore.
- The Hard Way: Forcing an AI agent to understand and correctly invoke this 18-parameter monstrosity. The agent acts as a glorified syntax checker, bound by the limitations of human-written code from a decade ago.
- The Soft Way (Semantic Reflection): We stop treating the PHP file as the "System." The Agent projects Intent (e.g., "Enroll Member 5 in Class 10") directly onto the data substrate.
The Core Shift
We must move from building rigid APIs (Gatekeeping) to building a Semantic Atlas (Observation and Intent).
The Agent doesn't read the code; it reads the Lore (the semantic map of the database) and validates its actions against Invariants. We decouple the outcome from the mechanism.