
Modeling hospital procurement bidding: lessons from my graduation project
A ~30-step public bidding process in software: one record from proposal to acceptance, JSON phases with defaults, and acceptance as one transaction.
Tag archive

A ~30-step public bidding process in software: one record from proposal to acceptance, JSON phases with defaults, and acceptance as one transaction.
Agent-generated codebases pass every structural-modularity metric while fragmenting the domain concept the team was trying to encode. Coverage measured whether a line ran. Mutation score measured whether an assertion pinned behavior. Cohesion is the next axis, and it measures whether the codebase's concepts are traversable end-to-end.

Multi-agent rename tooling rewrites two hundred files in ten seconds because it noticed the drift. Half the time the drift was a load-bearing distinction the team encoded on purpose. Vocabulary curation is a real-time review surface now, and senior includes refusing changes that would be technically more consistent because the domain has two concepts the agent has no way to see.
The bug I kept designing around was not "wrong penalty amount." Wrong amounts are visible. A supplier sees a credit note for EUR 8400,…
The RAG Platform returns 12 obligations from a signed MSA. Nine of them are real payment schedules...
Why Continuous Domain Modeling Is Essential There is a persistent, damaging misconception...
Introduction In the first article I explained in detail why it is important to have a good...