Skip to content

System landscape

The diagram shows responsibilities and communication paths. Provider arrows describe dependencies; they do not assert that every integration is enabled or that every operation uses the same adapter.

flowchart TD
People[Office, worker, customer and UE users] --> Web[Role-specific React application]
AI[Authorized external AI clients] --> MCP[Toolora MCP endpoint]
Web --> Supabase[Supabase Auth, PostgreSQL and Storage]
Web --> API[FastAPI]
MCP --> API
API --> Services[Domain and provider services]
Jobs[Schedulers and background work] --> Services
Services --> Supabase
Services --> Accounting[Accounting adapter / Fortnox]
Services --> Archive[Estate Data Hub archive contracts]
Services --> Delivery[Email, SMS and model providers]
Git[GitHub code and checks] --> Release[Exact-commit release tooling]
Release --> Web
Release --> API
Toolora's logical landscape. The handbook itself is a standalone static artifact.
Component Responsibility Boundary
React application Role surfaces, navigation, forms, tenant-aware query hooks and cache Browser configuration contains public client values; UI visibility does not authorize access
Supabase Auth Authentication and sessions used by browser and API callers Verified identity is combined with active membership and resource-specific policy
PostgreSQL and its API Records, RLS, constraints and transactional functions Direct browser operations remain subject to RLS; privileged server access requires separate checks
Storage Scoped application files and authorized retrieval Object paths, resource relationships and signed URL handling are part of access control
FastAPI Privileged portals, transactions, integrations and external effects Identity, capabilities and resource scope precede privileged business work
Services and schedulers Reusable domain behaviour, provider adapters and scheduled processing Success, retry and freshness semantics belong to each owning flow
Public MCP Caller-authorized reads and supported proposal operations The current tool contract is docs/mcp/contract.md; tools/list describes a connected server
GitHub and release tooling Reviewed code, selected checks and exact-commit builds/releases Running components may differ from main and from each other
Dependency Toolora’s use Ownership and limits
Fortnox / accounting interface Invoice operations and financial projections Provider evidence remains distinct from Toolora workflow state; shared connector adoption is incomplete for invoice writes
Estate Data Hub Preserved mail sources, bounded projections and document evidence Estate owns archive originals and source coverage; Toolora enforces its own reader policy
Resend and Twilio adapters Application email and SMS A queued intent, provider acknowledgement and recipient outcome must be documented separately
Anthropic adapter Supported AI assistance and proposals Authorized context and human confirmation boundaries remain Toolora responsibilities
Address search Structured address suggestions Manual input remains available; selection must be explicit
Bygglet import sources Historical and transition data Source provenance does not by itself prove native agreement or financial authority

This is an overview of source-declared dependencies. Provider configuration, credential references, rate limits, retry rules and exact enabled operations are deferred to the integration catalogue. No credentials or customer data are required to build this handbook.

External dependency ownership maps provider responsibilities to current clients and explains configuration and availability limits.

The deployment contract declares Caddy serving the frontend and proxying the application’s Supabase paths. The API is a separate systemd-managed FastAPI service on AX42. The marketing site is a separate runtime concern.

Public entry Declared responsibility
app.toolora.se Shared frontend and proxied Supabase paths
api.toolora.se Privileged API and public MCP endpoint
toolora.se, www.toolora.se Marketing site

Exact internal paths, ports, release commands, locks and rollback procedures are owned by docs/DEPLOY.md and its linked runbooks. This chapter summarizes their architecture and does not replace those procedures.

Runtime entry points gives the detailed contract, examples and evidence limits.

The map describes the repository-declared topology. Current runtime versions and provider enablement require observations of the relevant components. The operations overview distinguishes those observations from workflow and recovery evidence.