Product and shared infrastructure ownership
Toolora owns product behaviour and domain language. Shared infrastructure owns reusable capabilities where an accepted contract already exists. Adoption requires an explicit Toolora-owned boundary and verification against a real product workflow. A shared implementation’s existence does not prove that Toolora has adopted every operation it offers.
Integration ownership describes provider-facing responsibilities. This concept connects them to runtime, backup and operational ownership without creating a second infrastructure plan.
Responsibility reference
Section titled “Responsibility reference”| Capability | Shared responsibility | Toolora responsibility |
|---|---|---|
| Backup and recovery tooling | Estate implementation, inventory and generation-bound component evidence | Declare required data/identity coverage and verify application recovery |
| Secret delivery | Accepted source, installed broker and protected consumer mechanism | Component-specific input contract, runtime identity and affected-function verification |
| Mail originals | Archive preservation and documented read contract | Authorized selection, bounded projections, candidate review and business linkage |
| Fortnox connector | Shared credential, rate-budget and read-feed contracts | Company/destination identity, value reconciliation and product authorization |
| Accounting writes | Connector command coverage where actually available | Existing provider-neutral interface and in-process invoice adapter until a measured cutover |
| System meaning | Estate discovery and Dotiverse relationship context | Current accepted product contracts, source verification and precise local terminology |
Discover before adding a mechanism
Section titled “Discover before adding a mechanism”When a change touches a reusable integration, collector, data flow or agent surface, consult Estate for existing implementations and Dotiverse for their intended relationships. Read the current owning contract before designing a local alternative. Inventory and graph observations are discovery aids with their own dates; they cannot override the repository’s current working agreement or establish deployment status.
Adopt the smallest useful seam. Define required identity, data shape, freshness, failure and evidence at the Toolora boundary. Do not copy a legacy implementation or generalize a platform ahead of an observed need. The shared-infrastructure adoption document is explicitly a proposal: its suggested order is not an instruction to execute every migration.
Existing and proposed accounting paths
Section titled “Existing and proposed accounting paths”The Fortnox connector owns shared credentials, rate budgets and read feeds. Toolora still has an in-process invoice adapter behind a provider-neutral accounting interface. Do not describe connector adoption as a completed invoice-write cutover, and do not add a new direct Toolora-to-Fortnox call.
A measured replacement starts with a read-only shadow projection from the connector’s documented event contract. Compare identity, amounts and freshness with the current Toolora projection. Cut over only when those checks agree and the required command contract exists. Toolora retains business rules, authorization, reconciliation and uncertainty handling even after transport moves to a shared service. Accounting and external outcomes own those details.
Recovery and configuration ownership
Section titled “Recovery and configuration ownership”A database backup result is not a reason to build another backup tool, nor proof of combined application recovery. Use the estate’s generation-bound evidence and identify missing identity, Storage, decryption and startup checks. Recovery owns the acceptance boundary.
Similarly, use the installed broker for configuration. A local dotenv file or an old Infisical login is not an alternative runtime source. Runtime configuration describes identities; credentials describes replacement and exposure handling.
Synthetic adoption example
Section titled “Synthetic adoption example”A proposed invoice-status projection can consume a shared read feed without sending an invoice. It still needs exact company mapping, checkpoint/freshness handling and a comparison against the owning accounting record. A matching status string with a different provider company is a failed adoption check. Retain the existing write path until command coverage and scoped evidence permit replacement.
Documentation of this boundary authorizes no new feed, binding change, real bookkeeping, shared restore or private-data export. Decision authority distinguishes proposals, accepted contracts and observations so later maintenance can update adoption status without inventing a completed cutover.