Autonomous ERP design hinges on permitted object transitions, not shared screens

This engineering note argues that an autonomous ERP architecture for SAP and Joule integration must be validated in the target edition and authorized tenant before relying on it. It contends that a shared screen can make unrelated findings, invoices and exceptions look connected, so the design should instead trace each object, its evidence and its authority through permitted transitions. The author recommends defining an object spine first, including source system, tenant, native keys and mapping metadata, before building any agent catalog. It also separates the investigation model used for navigation from a transaction contract that specifies permitted operations, preconditions, approvals and expected outcomes. Authorization is to remain outside model reasoning, with instructions embedded in retrieved evidence unable to widen tool scope, and each SAP adapter requires its own acceptance testing.