Skip to content

Development targets and external effects

Toolora is in pre-launch development. The shared environment is https://app.toolora.se with https://api.toolora.se, using the Vi Målar tenant for shared functional checks. Its records are development data, but some configured providers have real external effects. The environment label does not make those effects synthetic.

The repository’s environment and provider contracts own permitted targets. A handbook build or a historical release receipt cannot override them. Check the current binding and affected operation before any provider-facing scenario.

Target or operation Current contract Consequence for verification
Local automated suites and disposable CI Local Supabase/fixtures selected by stack-owned commands Resets, seeds and synthetic database tests stay here
Shared application Vi Målar on the public app/API pair Reuse persistent staff/worker identities and saved sessions when functional work is needed
Vi Målar accounting binding Real Fortnox company 1160465 since November 11 Never initiate final attest, export or send as a test
Approved Fortnox write-test company DEV company 1026975; no Toolora tenant is bound at this source revision Do not change bindings or test against Vi Målar to bypass the missing target
Approved-time handoff A time approval can queue a downstream payroll action Treat the approval as an external-effect boundary, not a harmless editor test
Outbound email and SMS Actual configured delivery services Use the owning flow and controlled recipients for an explicitly needed test
Historical import cleanup and operational transition Deferred until the platform is ready Documentation work does not initiate cleanup, replacement import or cutover

test.toolora.se, dev.toolora.se and another hosted preview are not supported substitutes. Automated fixtures must not use the shared database. Database/reset tools obtain their target from the local stack rather than accepting an arbitrary caller-supplied database URL.

Source review, application checks and publication

Section titled “Source review, application checks and publication”

A source review can inspect policy, tests, migrations and presentation without creating users or reading private message bodies. The independent handbook needs no Toolora account, database or provider credential. Its build and browser tests validate the documentation reader flow.

An application change has a different obligation: focused tests, a pushed exact commit, publication of affected components through the accepted release path, and verification of the changed behaviour. The release contract preserves existing published work, health checks, locks and schema compatibility. A source SHA, a merged SHA and a deployed component SHA can differ.

When shared functional work is needed, the access runbook prepares the established identities and browser sessions. Its receipts prove the recorded scenario and version. They do not grant authority to repeat an external write or expand the test into unrelated provider operations.

In a synthetic case, a documentation author needs to explain the invoice editor’s preview and save states. They can inspect the editor, deterministic tests and local rendering fixtures. That does not require exporting an invoice, sending mail or making a final accounting attest in Vi Målar.

If an authorized application fix changes a real delivery action, the test must identify its exact recipient, provider target and recovery contract. A timeout does not establish that no message or accounting entry exists. Uncertain outcomes require the owning integration recovery before retrying.

The public frontend /version.json and API /version identify those running components. /healthz establishes liveness; /readyz checks named readiness dependencies. None of these signals independently proves the schema ledger, the provider binding, all business flows or recovery capability. Runtime entry points maps their owners.

This article records the reviewed environment contract, not a permanent current-version claim. Current publication observations and actual tests belong in the packet PR. A future operational transition requires its own accepted decision and updated owning environment document.