Topic map
The topic register assigns each subject a reader question, an article type and a canonical address. All 85 detailed answers are reviewed; preserved summaries link to their owning articles. Review depth describes writing, not independent product acceptance. The table is generated from COVERAGE.yaml.
Follow Documentation structure when splitting a topic into a separate article. Keep the previous summary anchor as a link to the new article so existing references remain useful.
Purpose and boundaries
What work does Toolora support, and where do its responsibilities end?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Product purposepurpose/product | Who uses Toolora, and which work does it connect? | concept | reviewed |
Actors and responsibilitiespurpose/actors | Which actors participate in Toolora workflows? | reference | reviewed |
Ownership across system boundariespurpose/ownership | Which records and outcomes belong to external systems? | concept | reviewed |
Current environment boundarypurpose/environment | Which shared checks can have real external effects? | reference | reviewed |
Landscape and architecture
How do application components, data paths and policy boundaries fit together?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Two application data pathsarchitecture/data-paths | When does an operation use RLS or the privileged API? | concept | reviewed |
Identity, company context and resource authorityarchitecture/authorization | Where is caller authority established? | concept | reviewed |
Transaction and external-effect boundariesarchitecture/transactions | Which changes can be committed atomically? | concept | reviewed |
Declared runtime topologyarchitecture/runtime | Which public entry point serves each component? | reference | reviewed |
External dependency ownershiparchitecture/providers | Which external records and services does Toolora depend on? | reference | reviewed |
Domain model and vocabulary
Which business records does Toolora distinguish, and how are they related?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Customers and contactsdomain/customers | How do customers, contacts and recipient roles differ? | concept | reviewed |
Projects and work ordersdomain/projects | What belongs to a project, and what belongs to a work order? | concept | reviewed |
Source offers and accepted agreementsdomain/agreements | Which relationship establishes commercial authority? | concept | reviewed |
Publication and record ownershipdomain/publication | How does publication affect a project record? | concept | reviewed |
Identity, companies and authorization
Where does Toolora decide whether a caller may read or change a record?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Authentication and sessionsaccess/identity | How does a request obtain a verified identity? | concept | reviewed |
Active company and membershipaccess/company | How is the company context selected and preserved? | concept | reviewed |
Capabilities and resource accessaccess/permissions | Why is a capability insufficient to authorize an operation on a particular record? | concept | reviewed |
Customer portal accessaccess/customer-portal | Which checks govern access to customer project information? | concept | reviewed |
Worker and subcontractor accessaccess/assignments | How do assignments limit worker and subcontractor access? | concept | reviewed |
MCP authorizationaccess/mcp | Which permissions apply at MCP entry and on individual tools? | reference | reviewed |
End-to-end business workflows
How do commercial, operational and financial records change during a customer engagement?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Enquiry and quote acceptanceworkflows/quote-acceptance | How does a customer request become accepted commercial work? | concept | reviewed |
Planning, execution and reviewworkflows/execution | How does planned work become reviewed delivery evidence? | concept | reviewed |
Subcontractor requests and awardsworkflows/subcontracting | How does a subcontractor response become an awarded commitment? | concept | reviewed |
Invoicing and settlementworkflows/settlement | Which facts are needed to follow work through invoicing and settlement? | concept | reviewed |
User interfaces
How do the role surfaces present authorized work and its current state?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Office workspacesexperience/office | Which work is organized in the office interface? | concept | reviewed |
Customer, worker and subcontractor surfacesexperience/portals | How do the portals differ in scope? | concept | reviewed |
Editing and conflict statesexperience/editing | How does the interface explain saves and concurrent changes? | concept | reviewed |
Responsive layout and accessibilityexperience/presentation | Which presentation rules apply across devices and themes? | reference | reviewed |
Frontend implementation
How are routes, state and data operations organized in the browser application?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Routes and role surfacesfrontend/routes | Where do application navigation and role-specific pages begin? | reference | reviewed |
Company-scoped queries and cachefrontend/cache | How is query state separated between companies? | concept | reviewed |
Mutations and concurrent editsfrontend/mutations | How do browser edits reach the owning transaction? | concept | reviewed |
Configuration and generated typesfrontend/configuration | Which configuration and type information belongs in the frontend? | reference | reviewed |
API and application services
Which operations belong in FastAPI, and how are their contracts enforced?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Route policy and resource scopeapi/policy | What must a privileged handler verify before business work? | concept | reviewed |
Request and response contractsapi/contracts | Where are inputs, outputs and errors defined? | reference | reviewed |
Domain and provider servicesapi/services | How is reusable server behaviour separated from HTTP handling? | concept | reviewed |
Conflicts and uncertain outcomesapi/errors | How should a caller interpret a conflict or an uncertain provider result? | troubleshooting | reviewed |
Data model and database
Where are persistent records, access policies and transactional invariants defined?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Records, relationships and projectionsdatabase/records | Which data is authoritative for a business fact? | concept | reviewed |
Row-level securitydatabase/rls | Which boundary governs direct browser data access? | concept | reviewed |
Functions and transaction boundariesdatabase/transactions | Where must multi-record invariants be enforced? | reference | reviewed |
Migrations and generated typesdatabase/migrations | How is a schema change prepared and released? | procedure | reviewed |
Files, documents and communication
How are files, originals and communications scoped and published?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Storage and signed linksdocuments/storage | How do file paths and retrieval links preserve access scope? | reference | reviewed |
Conversation audiencesdocuments/audiences | Who may read a project or work conversation? | concept | reviewed |
Mail originals and attachment evidencedocuments/originals | Which system preserves mail originals and their coverage? | concept | reviewed |
Document candidates and interpretationdocuments/intake | When does a preserved attachment become business data? | concept | reviewed |
Finance and reconciliation
Which records establish amounts, financial authority and reconciliation status?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Billing basis and invoicesfinance/billing-basis | How is accepted commercial value made available for invoicing? | concept | reviewed |
ROT and RUT allocationsfinance/deductions | Which facts determine household-work deduction evidence? | reference | reviewed |
Payments and reconciliationfinance/reconciliation | What supports a conclusion about payment and outstanding balance? | concept | reviewed |
Purchase costs and allocationsfinance/costs | How can one supplier cost be attributed to several projects? | concept | reviewed |
Time and payroll handofffinance/time-payroll | Which time is eligible for a payroll handoff? | concept | reviewed |
Reports and amount definitionsfinance/reports | How do report datasets determine totals and coverage? | reference | reviewed |
Integrations and shared services
Which external contracts does Toolora consume, and who owns their data and outcomes?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Integration ownershipintegrations/ownership | Which responsibilities remain in Toolora when a shared service is used? | concept | reviewed |
Accounting and Fortnoxintegrations/accounting | Which accounting responsibilities belong to the connector and the local adapter? | reference | reviewed |
Estate mail archiveintegrations/mail | What does Toolora read from the mail archive? | reference | reviewed |
Retries and external outcomesintegrations/recovery | How can an integration recover without repeating an uncertain action? | troubleshooting | reviewed |
AI, assistant and MCP
What context may AI clients read, and when can a proposal change business records?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
MCP tools and responsesai/mcp | Which contract describes the current public MCP interface? | reference | reviewed |
Context and source evidenceai/context | How is source information bounded before model use? | concept | reviewed |
Proposals and human confirmationai/proposals | When does an AI proposal become an ordinary business record? | concept | reviewed |
Usage, audit and feedbackai/governance | How are tool use and unsupported requests accounted for? | reference | reviewed |
Background work and change feeds
Which work continues outside an interactive request, and how is progress represented?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Schedulers and enablementbackground/schedulers | Where are scheduled jobs registered and enabled? | reference | reviewed |
Intent, processing and receiptsbackground/outcomes | How do queued work and completed outcomes differ? | concept | reviewed |
Change feeds and checkpointsbackground/changes | How does a caller resume authorized change tracking? | reference | reviewed |
Stalled work and diagnosisbackground/stalled | What evidence distinguishes an idle job from blocked business work? | troubleshooting | reviewed |
Import, history and data quality
How does imported history preserve identity and business meaning without creating new effects?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Preserved sources and identifiersimports/sources | Which source identity must survive an import? | reference | reviewed |
Historical replay and side effectsimports/replay | Why must replayed history avoid forward-looking notifications? | concept | reviewed |
Identity, relation and value checksimports/reconciliation | What must reconciliation establish beyond matching row counts? | reference | reviewed |
Operational transitionimports/cutover | When does Toolora become the system of action for new work? | concept | reviewed |
Security and information handling
Which controls protect identity, company isolation and sensitive information?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Trust boundaries and privileged accesssecurity/trust | Where does an operation cross into a more privileged context? | concept | reviewed |
Credentials and configurationsecurity/credentials | Where do secret values belong, and how are replacements verified? | reference | reviewed |
Personal data, originals and retentionsecurity/data | Which data lifecycle rules apply to records and attachments? | reference | reviewed |
Audit, logs and incident evidencesecurity/logs | What can be recorded without copying sensitive content? | reference | reviewed |
Infrastructure and runtime
Where do Toolora components run, and which configuration and platform responsibilities support them?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Runtime components and servicesinfrastructure/services | Which runtime component serves each application entry point? | reference | reviewed |
Configuration and service identitiesinfrastructure/configuration | How do runtime identities obtain their component configuration? | reference | reviewed |
Release directories and publicationinfrastructure/publication | How is a built candidate made current? | concept | reviewed |
Shared infrastructure ownershipinfrastructure/ownership | Which capabilities should Toolora consume rather than reproduce? | concept | reviewed |
Development, testing and delivery
How does a change move from local implementation to an identified, checked release?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Local development and synthetic datadelivery/local | How is an isolated development environment prepared? | procedure | reviewed |
Test levels and evidencedelivery/tests | Which checks run automatically, and what can they prove? | reference | reviewed |
Pull requests and application releasedelivery/releases | How is a coherent change reviewed and published? | procedure | reviewed |
Schema delivery and compatibilitydelivery/schema | How do database changes remain compatible with application publication? | procedure | reviewed |
Monitoring, diagnosis and recovery
How are failures detected, investigated and recovered with evidence?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Health, readiness and versionsoperations/health | What does each runtime signal establish? | reference | reviewed |
Workflow diagnosisoperations/diagnosis | How is an observed failure traced to its owning component or record? | troubleshooting | reviewed |
Backup and recovery evidenceoperations/recovery | What must a recovery check include before an application outcome is claimed? | procedure | reviewed |
Incident responseoperations/incidents | How is an incident contained and its recovery verified? | procedure | reviewed |
Decisions, limitations and system status
Which sources establish decisions, current limitations and verified delivery status?
| Topic | Reader question | Article type | Detail status |
|---|---|---|---|
Document ownership and decisionsdecisions/authority | Which source owns a rule when documents disagree? | reference | reviewed |
Known limits and open decisionsdecisions/limits | How are unresolved definitions and missing evidence represented? | reference | reviewed |
Implementation and release statusdecisions/status | How do implemented, merged, deployed and verified states differ? | concept | reviewed |
Scenario evidence and coveragedecisions/evidence | How should a reader interpret a test or delivery receipt? | reference | reviewed |