Skip to content

Purpose and system boundaries

Toolora is a multi-tenant operations platform for Swedish painting and service companies. It connects customer relationships, commercial agreements, delivery work and financial follow-up. Separate staff, worker, customer and subcontractor surfaces expose the parts of that work each actor is authorized to use.

The project is the shared business context for a customer outcome. It can exist before an accepted quote and connects work without making all related records one object. An accepted quote, a work order, a calendar allocation and an invoice each carry their own meaning and lifecycle.

Product purpose and connected work gives the detailed contract, examples and evidence limits.

Actor Main concern Authority remains bounded by
Office staff and company administrators Customers, offers, planning, project follow-up and financial review Active company, capabilities and resource scope
Employees using the worker surface Assigned work, daily execution and their own time Assignment, publication and worker-specific policies
Customer contacts Offered terms and authorized project collaboration Public quote-token authority or separately granted authenticated portal access
Subcontractors (UE) Scoped requests, awarded work and submissions Their own company, invitation/commitment scope and visibility policies
Platform administrators Platform-level administration Explicit privileged policy and selected resource/company context
AI clients and assistants Read authorized context and prepare supported proposals Caller permissions, tool contracts and human confirmation boundaries

These are product audiences, not a complete capability matrix. The detailed actor reference and access articles identify their separate authority boundaries.

Actors and authority contexts gives the detailed contract, examples and evidence limits.

The main journey connects a customer need to a proposal, agreement, project delivery, financial basis and settlement. Related work includes worker planning, time reporting and attestation, UE procurement and review, documents and dialogue, purchase-cost allocation and reporting. The records change through explicit actions and preserve their separate states.

Several distinctions determine correct behaviour:

  • A customer is an organization or household. Its contact, quote recipient, invoice recipient and deduction recipients are separate roles.
  • A work site is separate from the customer’s postal address. Moving a customer must not silently move the intended job.
  • A source-offer link records provenance. An accepted billing quote authorizes commercial basis; the first link alone does not establish acceptance.
  • Planned hours, reported hours and approved hours are different facts.
  • Publication controls visibility. It does not establish that work is complete.
  • A staff-confirmed AI proposal can create a native editable quote. Sending it and recording the customer’s acceptance are separate decisions.
  • Invoice transfer, customer delivery, bookkeeping, payment and deduction authority outcomes require their own evidence.

CONTEXT.md owns these definitions. The domain model describes the relationships, including customer roles and accepted agreements.

Toolora owns product behaviour, its operational records and user-facing domain language. PostgreSQL, Auth and Storage hold the application’s persistent state. External providers retain their own records and outcome evidence.

The accounting integration is behind a provider-neutral interface. The shared Fortnox connector owns shared credential, rate-budget and read-feed contracts; Toolora still has an in-process invoice adapter. A complete invoice-write cutover to the connector is not established by the repository agreement.

Company mail is a read-only view of Estate Data Hub’s archive. Estate owns preserved originals and attachment bytes; Toolora maintains a bounded projection. That workspace does not send or reply to mail. Toolora’s own quote, invoice and project notification deliveries belong to their respective workflows.

Approved-time handoff and payroll processing are also distinct responsibilities. The domain contract assigns payroll processing to the accounting bureau; enabled formats, mappings and real receiving-system acceptance need their own evidence.

System ownership identifies canonical business facts, external observations and the identity that must survive an integration boundary.

The working agreement describes Toolora as pre-launch. Shared functional checks use Vi Målar at app.toolora.se and api.toolora.se. Automated resets, seeds and database suites use local Supabase or disposable CI databases.

Since 2026-11-11, Vi Målar is bound to its real Fortnox company. A final attest, export or send to that company is real bookkeeping and must not be initiated as a test. The only authorized Fortnox write-test target is the separate DEV company identified in the environment contract. At this reviewed source revision no Toolora tenant is bound to that target.

This is an environment contract, not a live deployment observation. Current bindings, versions and operational transition decisions must be checked before work that depends on them.

Development targets and external effects gives the detailed contract, examples and evidence limits.