BusDK Docs
BusDK Docs
  • Get started ▸
    • Overview
    • Design goals and requirements
    • Development status
      • Accounting workflow
      • Sale invoicing
      • Inventory valuation
      • Spreadsheet workbooks
      • Finnish bookkeeping and tax
      • Finnish company reorganisation
      • Developer workflow (Cursor)
      • Developer workflow (Gemini)
      • Developer workflow (Claude)
      • Developer workflow (Codex)
      • Finnish payroll
      • Orphan modules
    • Regulated report PDFs (TASE, tuloslaskelma)
    • Finnish WebView UI requirements
    • Go optimization guide
    • 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
  • Modules ▸
    • Modules overview
    • Module feature table
    • bus
    • bus init
    • bus config
    • bus data
    • bus api
    • bus sheets
    • bus dev
    • bus agent
    • bus secrets
    • bus bfl
    • bus accounts
    • bus entities
    • bus period
    • bus preferences
    • 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
  • Software Design Documents ▸
    • SDD overview
    • bus
    • bus init
    • bus config
    • bus data
    • bus api
    • bus sheets
    • bus dev
    • bus agent
    • bus secrets
    • bus bfl
    • bus accounts
    • bus entities
    • bus period
    • bus preferences
    • 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
  • 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 closing deadlines and legal milestones
    • Finnish closing checklist and reconciliations
    • Finnish closing adjustments and evidence controls
    • Finnish company reorganisation (yrityssaneeraus)

Design goals and requirements

BusDK Design Spec: Design goals and requirements

This section is split into single-concept documents:

AI-readiness (objective, not dependency), Auditability and append-only discipline, CLI-first and human-friendly interfaces, and Deterministic .bus command files define core execution principles.

Double-entry ledger accounting, Extensibility as a first-class goal, Initial feature scope (modules), and Git as the canonical, append-only source of truth define scope and architecture constraints.

Modularity as a first-class requirement, Plain-text CSV for longevity, Schema-driven data contract (Frictionless Table Schema), and Unix-style composability (micro-tools) define data and integration properties.

← Visual identity and branding on outputs BusDK Docs AI-readiness (objective, not dependency) →

Sources

  • Design goals index
  • Architectural overview
  • Purpose and scope
Improve this page BusDK · GitHub · Releases · Issues © 2026 Heusala Group Ltd