Integration ownership
Toolora owns its product behavior, domain decisions and authorization at each integration seam. A shared service owns only the capability defined by its contract. Reusing a service therefore requires an explicit mapping of identities, commands, observations and failure states; it does not move all business authority to that service.
Responsibility at the seam
Section titled “Responsibility at the seam”| Boundary | Shared or external responsibility | Toolora responsibility |
|---|---|---|
| Mail archive | Preserve source metadata/originals and report source coverage | Attest the company binding, enforce reader policy, project bounded content and preserve gaps |
| Accounting connector | Credential custody, coordinated provider budget, command/read-feed contract | Approve and freeze the business action, bind the provider company, retain/reconcile receipts |
| Auth and database infrastructure | Validate sessions and execute configured grants/policies | Define live actor eligibility, capabilities and resource admission |
| Message/model provider | Execute the admitted provider request and return its observation | Choose permitted content, sender/recipient, budget and review workflow |
The ownership concept distinguishes canonical business facts from copies and observations. External providers identifies representative client implementations. Shared infrastructure is a routing and reuse direction; the adoption proposal alone does not prove that a specific workflow has already moved to a shared command path.
What a Toolora-owned contract includes
Section titled “What a Toolora-owned contract includes”A useful seam names the company/account mapping, stable resource/command identity, permitted operations, expected schema/version, current observation time, coverage and error semantics. Caller authority must be established before a server-held credential is used. The adapter then validates the external identity and returned facts before writing Toolora’s projection.
The accounting payment feed, for example, validates the mapped connector company, opaque event cursor, event envelope and payment identity/value fields. A source content hash supports provenance; it is not a freshness or payment-completeness certificate. The mail archive binding similarly checks account/cell/connection identity instead of accepting a browser-provided source reference.
Adoption and coexistence
Section titled “Adoption and coexistence”Current accounting adoption is intentionally mixed. The shared connector supplies selected AP/payroll command and payment-feed contracts, while Toolora retains an in-process invoice adapter behind its provider-neutral interface. It would be incorrect to describe either every accounting operation as local or the invoice write cutover as complete. See the accounting reference.
When a shared capability is considered, use Estate to locate the implementation and Dotiverse to recover the recorded relationships, then verify the current contract and actual Toolora caller. Inventory liveness and graph observations are not release or environment authority. The current repository’s pre-launch and real-provider restrictions override historical descriptions of operational use. Do not copy legacy implementations or create a generic platform mechanism before a concrete seam is needed.
Failure and change ownership
Section titled “Failure and change ownership”An unavailable shared service should produce an operation-specific failure or partial result. Toolora must not silently manufacture a complete projection or switch to another provider/company. An ambiguous command requires readback or reconciliation using its existing identity. A schema or contract mismatch requires a controlled compatibility decision, not a catch-all retry.
For synthetic Binding A, a changed archive connection is an identity mismatch even if the mailbox address is unchanged. For synthetic Command B, a timeout does not permit another independently keyed export. These boundaries are exercised with substituted clients in focused tests; shared service adoption requires its own identity, value and freshness evidence. This review creates no new integration or provider action. Recovery owns the next diagnostic steps, and transactions owns local atomicity.