Define the object spine and action contract
A shared enterprise screen can make a maintenance finding, a customer invoice and a finance exception look connected. The architecture earns its value when a reviewer can follow the object, the evidence and the authority through the next permitted transition. A common status name alone cannot establish that two systems mean the same thing.
Define the object spine before the agent catalog. For an equipment record, include source system, tenant or client and the native equipment key. For an accounting item, retain company, fiscal year, document and line item. Store source revision, valid time and data owner on material mappings. Model relationships such as finding-to-work, delivery-to-billing and billing-to-accounting with the evidence that supports each link.
Separate the investigation model from the transaction contract. The investigation model can help an operator navigate related objects and compare evidence. The transaction contract names a permitted operation, its preconditions, required role or approval, exact input revision and expected target state. This is the contract that a web application, scheduled worker or conversational skill must satisfy before dispatch.
Qualify clean-core extensions and trust
On SAP, choose the released API and supported extension point for the target landscape. The clean-core review should record the release status, allowed extension classification and upgrade obligations. SAP's current Cloud ALM documentation distinguishes several extension levels. The architecture team should classify the actual dependency instead of treating every classic extension as an equivalent risk.
A proposed BTP boundary uses supported destinations and trust, narrow API exposure and integration flows where mappings or protocol conversion are needed. Use user authority where the topology supports it and restricted technical identities for background work. Confirm backend authorizations under both permitted and restricted users. Keep model reasoning outside the authorization decision. An instruction embedded in retrieved evidence must never expand a tool's scope.
Retain outcomes and bound agent tools
An action record retains request identity, target environment, object revision, approval evidence and outcome. If a response is lost after dispatch, recovery starts by establishing whether the target acted. The nine local controller tests demonstrated selected authority, replay and reconciliation behaviors in temporary fixtures. Each SAP adapter still needs its own acceptance run for actual commit, error, concurrency and authorization semantics.
Use a Joule skill for a bounded task once the ordinary application route works. Use an agent for contextual investigation through permitted tools. The newer managed Studio and classic edition have different setup and availability conditions. Confirm the chosen product, edition and consumption model. The first skill might retrieve a linked work-order case. A write-capable skill should invoke the same controlled action and return the same authoritative reference as the workspace.
Release against an evidence gate
The first release gate should include an approved path, a denied role, stale input, duplicate dispatch, timeout and manual recovery. Record verified completion and unresolved outcomes alongside handling time. Repeat the evidence pack when a model, tool, policy or SAP release changes. AssetSolve Autonomous ERP applies these principles to a scoped implementation.