External dependency ownership
External dependencies enter Toolora through specific server-side clients and services. They supply authentication, stored content, communications, model responses or accounting observations. The table identifies the current code boundary; configuration, an installed adapter and a successful business scenario remain separate evidence.
Dependency inventory
Section titled “Dependency inventory”| Dependency | Reviewed client or service | Contract and limitation |
|---|---|---|
| Supabase Auth, PostgreSQL, PostgREST and Storage | supabase_admin, browser Supabase client, active migrations |
Identity, caller data access and privileged operations use different execution roles. The shared stack is self-hosted. |
| Estate mail archive | estate_mail_archive, mail_intake_client |
Account-bound metadata/original retrieval. Toolora does not connect directly to a mailbox protocol or send replies from this workspace. |
| Shared accounting connector | accounting_connector, AP/payroll workers, accounting_payment_feed |
Command submission/readback and opaque-cursor events. Toolora owns approval and validates the mapped company. |
| Existing Fortnox invoice integration | Provider-neutral accounting interface and services/fortnox |
Selected invoice exports and read/sync paths remain in-process. Connector adoption is incomplete. |
| Application email and SMS | Sending services and tenant messaging configuration | Operation-specific sender, enablement and delivery evidence. An SDK or configured credential does not enable every notification. |
| Anthropic model calls | services/ai and the relevant feature workers |
Bounded input, usage accounting and feature-specific review. Output is not business confirmation. |
| Website, address and matching services | Website synchronization, address routes, matching gateway | Separate product surfaces and scoped contracts; not alternative database or customer-connector authority. |
The integration articles own command, archive and recovery semantics. Storage owns retrieval identity and URL lifetime. Avoid interpreting this inventory as a list of enabled production features: source inspection does not observe a running configuration or provider account.
Credentials and resource identity
Section titled “Credentials and resource identity”Credentials remain in server/runtime configuration. The browser receives public configuration and its user’s session, not provider secrets or service-role keys. A backend client must bind the request to the selected company and resource before using privileged access. An external account reference is not accepted merely because the caller supplies it.
For mail setup, server-returned account/cell/connection identity is rechecked against the tenant directory. For accounting, the connector mapping and provider company fingerprint constrain the destination. These checks solve identity binding; caller authorization still decides who may request an action. Follow the current runtime configuration owner when replacing a secret; do not infer credentials from a stale checkout or evidence file.
Availability and failure
Section titled “Availability and failure”An unavailable dependency can leave Toolora healthy enough to serve other work. A readiness response, scheduler registration or HTTP acknowledgement cannot certify original-byte coverage, accounting completion or delivered email. Dependency errors must be interpreted at the owning operation: a refused precondition, an unknown submission and a stale read projection require different recovery.
For synthetic Source A, a visible mail row with unavailable RFC822 bytes is a partial source observation, not an empty original. For synthetic Export B, a timeout after submission can be ambiguous even if a retry would be easy to issue. Use coverage and outcome recovery rather than inventing a common retry rule.
Scope of the inventory
Section titled “Scope of the inventory”The current public application and API are separate entry points; public marketing, matching and historical prototype repositories do not become the authenticated application by sharing the Toolora name. The runtime/deployment owner retains its exact host/service commands. This reference identifies provider responsibilities and representative code paths, not a complete package/SBOM list or a certification of every external account. Tests with substituted clients prove local handling of their supplied responses; real provider behavior needs its own named evidence.