BusDK Docs
BusDK Docs
  • Get started ▸
    • Overview
    • Design goals and requirements
    • Cost summary
  • Workflows ▸
    • Accounting workflow overview
    • Sale invoicing (sending invoices to customers)
    • Example end-to-end workflow
    • Finnish payroll (monthly pay run)
    • CLI tooling and workflow
  • FAQ ▸
    • What are bus and BusDK?
    • Getting started and adoption
    • Workspaces, datasets, and compliance boundaries
    • AI assistants, automation, and safety
    • Modules, repositories, and contribution model
    • Purchasing and pricing
  • Modules ▸
    • Modules overview
    • Module capabilities
    • aiz
    • bus
    • bus init
    • bus config
    • bus data
    • bus api
    • bus sheets
    • bus dev
    • bus agent
    • bus secrets
    • bus bfl
    • bus accounts
    • bus entities
    • bus customers
    • bus vendors
    • bus period
    • bus preferences
    • bus files
    • bus attachments
    • bus invoices
    • bus journal
    • bus bank
    • bus reconcile
    • bus assets
    • bus loans
    • bus inventory
    • bus payroll
    • bus budget
    • bus reports
    • bus validate
    • bus vat
    • bus pdf
    • bus filing
    • bus filing prh
    • bus filing vero
    • bus gateway
  • Design ▸
    • System architecture
    • Data formats and storage
    • Data directory layout
  • Reference ▸
    • Master data
    • Integration and future interfaces
    • Extensibility model
    • Testing
    • References and foundations
  • Compliance ▸
    • Finnish bookkeeping and tax-audit
    • Finnish balance sheet and income statement regulation
    • Finnish reporting taxonomy and account classification
    • Household accounting and personal finance
    • Finnish closing deadlines and legal milestones
    • Finnish closing checklist and reconciliations
    • Finnish closing adjustments and evidence controls
    • Finnish company reorganisation (yrityssaneeraus)

BusDK Design Spec: System architecture

In this section

This section is split into single-concept documents:

Append-only discipline and security model, Architectural overview, CLI as the primary interface (controlled read/modify/write), and Git-backed data repository (the data store) define core runtime and storage architecture.

Independent modules (integration through shared datasets), Workspace scope and multi-workspace workflows, and Shared validation layer (schema + logical validation) define module boundaries and integration contracts.

← Unix-style composability (micro-tools) BusDK Docs Append-only discipline and security model →

Sources

  • Architecture index
  • Data directory layout (principles)
  • Design goals index
Improve this page BusDK · GitHub · Releases · Issues © 2026 Heusala Group Ltd