BusDK Docs
BusDK Docs
  • Get started ▸
    • Overview
    • Deployment and data control
    • No-spend worker testing
    • UpCloud and Stripe setup
    • Design goals and requirements
    • Cost summary
    • Go peer review guide
      • Review order
      • Ownership and architecture
      • API and type design
      • Source transforms and evaluators
      • Data mapping
      • Control flow and mutation
      • Destructive and batch operations
      • Errors and CLI diagnostics
      • Context, resources, and concurrency
      • Determinism and side effects
      • Workflows and backends
      • HTTP and service boundaries
      • Browser and UI boundaries
      • Validation and domain safety
      • Authentication and credentials
      • External runners
      • Performance review
      • Tests and evidence
      • Documentation and traceability
      • LLM finding patterns
      • Compact checklist
  • Reports ▸
    • Project reports
    • Development retrospective, 2026-05-20 to 2026-05-27
  • 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 api provider auth
    • bus api provider billing
    • bus api provider books
    • bus api provider cloud
    • bus api provider containers
    • bus api provider data
    • bus api provider database
    • bus api provider inference
    • bus api provider llm
    • bus api provider node
    • bus api provider session
    • bus api provider usage
    • bus api provider vm
    • bus auth
    • bus billing
    • bus operator
    • bus operator auth
    • bus operator billing
    • bus operator cloud
    • bus operator database
    • bus operator deploy
    • bus operator inference
    • bus operator node
    • bus operator stripe
    • bus operator token
    • bus sheets
    • bus dev
    • bus agent
    • bus run
    • bus remote
    • bus remote-control
    • bus work
    • 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
    • bus-gx
    • bus integration cloud
    • bus integration database
    • bus integration inference
    • bus integration billing
    • bus integration node
    • bus integration ollama
    • bus integration postgres
    • bus integration ssh runner
    • bus integration stripe
    • bus integration usage
    • bus integration upcloud
  • Design ▸
    • System architecture
    • UI framework
      • v0.1.1 Core node foundation
      • v0.1.2 GX source tools
      • v0.1.3 GX compiler
      • v0.1.4 Component calls
      • v0.1.5 Component composition
      • v0.1.6 Callback props
      • v0.1.7 Go WASM frontend runtime
      • v0.1.8 Runtime diagnostics
      • v0.1.9 Browser API boundaries
      • v0.1.10 Core test helpers
      • v0.1.11 WASM app acceptance
      • v0.1.12 Intrinsic callback naming
      • v0.1.13 Handle render scheduling
      • v0.1.14 Expanded intrinsic elements
      • v0.1.15 Typed event payloads
      • v0.1.16 Minimal browser adapters
      • v0.1.17 State runtime
      • v0.1.18 Effect runtime
      • v0.1.19 Event and form helpers
      • v0.1.20 UI testkit renderer
      • v0.1.21 UI testkit browser parity
      • v0.1.22 Action primitives
      • v0.1.23 Resource primitives
      • v0.1.24 Session primitives
      • v0.1.25 Portal context consumption
      • v0.1.26 Streaming ownership
      • v0.2.0 Bus UI module baseline
      • v0.2.1 Icons
      • v0.2.2 Buttons and links
      • v0.2.3 Menus and tabs
      • v0.2.4 Panels and cards
      • v0.2.5 Layout helpers
      • v0.2.6 Shells
      • v0.3.1 Forms
      • v0.3.2 Form fields
      • v0.3.3 Input controls
      • v0.3.4 Submit state
      • v0.3.5 Tables
      • v0.3.6 Lists
      • v0.3.7 Timelines
      • v0.3.8 Status surfaces
      • v0.4.1 Resources
      • fc-004 Runtime config and API URLs
      • fc-005 Sessions
      • fc-006 Credentials
      • fc-007 Provider errors
      • fc-008 Assets and host tools
      • fc-009 Assistant workbench shell
      • fc-010 Assistant threads and messages
      • fc-011 Assistant composer and attachments
      • fc-012 Assistant model selection
      • fc-013 Assistant review controls
      • fc-014 Terminal sessions
      • fc-015 Terminal IO
      • fc-016 Terminal approvals
      • fc-017 Terminal adapter
      • fc-018 Evidence URLs and links
      • fc-019 Evidence previews
      • fc-020 Projection details
      • fc-021 File drops
      • fc-022 Image galleries
      • fc-023 Component catalog
      • fc-024 GX and Go artifact metadata
      • fc-025 Product module integration
      • fc-026 Examples, testing, and release review
    • API JWT audiences and scopes
    • Data formats and storage
    • Data directory layout
  • Reference ▸
    • Master data
    • Integration and runtime interfaces
    • Deployment and data control
    • UpCloud and Stripe setup
    • 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 — CLI tooling and workflow

BusDK Design Spec: CLI tooling and workflow

This section is split into single-concept documents:

Extensible CLI surface and API parity, Git commit conventions per operation (external Git), Command structure and discoverability, Standard global flags, and CLI command naming define command design conventions.

Minimum required command surface (end-to-end workflow), Error handling, dry-run, and diagnostics, Non-interactive use and scripting, and Reporting and query commands define operation behavior.

For .bus usage, follow .bus files — getting started step by step, .bus getting started — multiple commands together, and .bus script files (writing and execution guide). Installation guidance for syntax highlighting in common editors is in Editor support for .bus files. Validation policies are in Validation and safety checks.

← VAT area (reference data and filed summaries) BusDK Docs Extensible CLI surface and API parity →

Sources

  • BusDK module CLI reference
  • Standard global flags
  • CLI command naming
Improve this page BusDK · GitHub · Releases · Issues © 2026 Heusala Group Ltd