Shift handover before the sitemap: what domain knowledge changes in batch management

In container-glass production a recipe is not a list of ingredients. It is a decision about temperature, redox, cost and what the next shift will find. Model that as form fields and you lose the order in which reality hits. First a version holds. Then weighing happens. Then the silo is lighter. Then the furnace has to match the calculation. Then the shift hands over. The screen that offers every field at once does not know that sequence.

Domain knowledge therefore changes the questions first. Not which screen is missing, but what must not silently disappear after weighing. What one shift must leave the next without a side calculation in someone’s head. Which figure still has to match the hall in the evening after three stations have written. Invariants follow from those questions. The model follows from the invariants. Screens follow from the model, not the other way round.

The technical consequences are rarely spectacular. Bookings become states. Calculations stay bound to versions. Validation is a step someone can see. Migrations and backups belong to the product. Shift start is a clock. None of that wins an architecture prize. All of it decides whether someone can still explain yesterday at six.

Without the domain, different defects appear, often late. A soft-delete that does not reverse the silo. A recipe change that writes into batches already weighed. A cost calculation that takes the open screen instead of the version at the scale. A shift handover that exists only as a comment field. Each point looks quiet in the demo. On the floor they add up to a night.

That is why someone who can explain the process belongs at the start of the architecture, not at the end of acceptance. Acceptance finds the missing button. It rarely finds the missing irreversibility. The most expensive defect is the one the system allows because nobody treated it as domain.

For clients and teams: ask for the explanation of the day before you ask for the explanation of the stack. If the day cannot be told, the software will not carry it either. If it can be told, the stack will look comparatively dull. In this field that is a good sign.