The Translation Penalty: Why One Rule Change Becomes Months of Repairs | Oryh

One business instruction changes. Why do forms, workflows, reports, and integrations all need repairs? This Oryh development note examines the translation penalty: the ongoing cost of keeping multiple technical interpretations synchronized with the business rules they represent. Using an illustrative purchasing-renewal scenario, it explores an alternative: agents read effective company-owned policies and current evidence, while software preserves records, rule versions, permissions, and audit history. Natural language does not eliminate engineering. Effective dates, scope, in-flight transactions, reliable integrations, deterministic controls, and human confirmation still matter. Rule editing must preserve existing provisions rather than replace an entire policy with one new condition. The aim is to improve reusable record and execution capabilities instead of accumulating customer-specific branches for every business change. The purchasing scenario is illustrative, not a customer incident. This is an architectural discussion, not a measured cost-saving claim. Oryh: https://www.oryh.ai Open source (Apache 2.0): https://github.com/AIE-enginehub/Oryh #Oryh #AIAgents #EnterpriseSoftware