Evolution over time (extending the model)
Evolution over time (extending the model)
As the business evolves, the workflow stays stable because the authoritative interface is the workspace datasets and their schemas. BusDK’s module boundaries allow you to extend what is recorded and computed without rewriting history.
-
When a new data need appears, Alice expresses it as a schema change and a corresponding record shape change, for example adding a currency field to the relevant table schemas and then adding the corresponding values to new records.
-
Alice runs validation to ensure the updated schemas and datasets remain consistent:
bus validate
- If the change affects derived outputs, she regenerates them deterministically from the updated repository data:
bus reports trial-balance --as-of 2026-12-31
- Alice records the evolution as a normal, reviewable change to repository data by creating a new revision with her version control tooling.
If Alice hires an assistant, the same sequence is executed through standard version control collaboration outside BusDK. If new taxes or reporting obligations appear, she adds the appropriate module and runs its commands against the same datasets, because “CSV plus schemas” remains the stable interface between modules and workflows.