I asked a coding agent to work on an Italian invoicing application. It produced an answer. Then I asked it to distil the domain: the concepts, rules and relationships behind the invoices. When we returned to the work, the same words finally had something shared behind them.

This session follows that before-and-after through recorded demonstrations on a real C# / ASP.NET application. We watch the agent investigate a business error, build a reusable account of the domain and use that knowledge to reason about a change. The turning point is the understanding we have made available to it.

Eric Evans’s idea of a ubiquitous language provides the connection: the need to share meaning now extends to the agents working alongside us. Italian invoicing is the example. The question you take home belongs to your own business: when you and your agent use the same words, do you mean the same thing?

For developers, architects and technical leads working with AI on business software. The before-and-after demonstration makes domain knowledge visible as an engineering concern. Attendees see how shared terminology gains meaning through rules and relationships, and how to carry that understanding into later work. The example is specific enough to inspect; the lesson applies across business domains.
Italian meetup recording: https://www.youtube.com/live/n6kYt_taBtM
Example code: https://github.com/lazyoft/raymond-invoices