Model your domain
Define the smallest shared model that gives your first agent or workflow reliable business context.
Start with the noun your team acts on most often: an account, invoice, shipment, request, or case. Define only what the first use case needs.
1. Define the entity
Name the entity, its stable identifier, the attributes a decision needs, and the relationships that make the answer meaningful. For an invoice, that might include amount, due date, status, customer, and the contract that governs it.
2. Map the sources
Map source fields to the entity rather than teaching every workflow a separate schema. Keep the source reference and last-sync information so an answer remains traceable to the system it came from.
3. Test real questions
Ask the questions the model must support. If the answer depends on an unmodelled relationship, add that relationship deliberately. Do not compensate for missing context with a longer agent brief.
Read Entities and relationships for the model itself.
Aktualisiert am 31. Aug. 2026