Room 10 of 10
Make the engineering traceable
Our question
How does a modeling choice change what a system can explain?
Back at Harbor Coffee
The waiting question led us to distinguish acceptance, component readiness, and handoffs. Those choices tell an engineer which records to retain. The records support an answer with a time window and limits; they do not prove a permanent bottleneck.
Around a whiteboard, firsthand sources retell stories and correct misunderstandings. With an engineer and AI, learned patterns can fill gaps as the conversation speeds up. Write the context, claims, sources, and unanswered questions down so both are reasoning about the same situation. Agreement between engineer and AI does not validate the account.
Try a modeling decision
Which handoff to engineering preserves the reasoning?
Choose a view to see what it makes visible.
On the whiteboard
- Purpose → How does a modeling choice change what a system can explain?
Read the worked explanation
Carry the purpose, model, evidence, definitions, revisions, and next questions into the work. Models can inform process design, data structures, APIs, knowledge graphs, ontologies, and AI context. This workshop follows one trace instead of treating each destination as a separate lesson.
Room not yet explored. Capstone progress is separate.
Inspect the source
Sam’s question
Participant accountsupportedCustomers tell us they wait too long in the morning. I want to understand what happens between taking an order and handing it over.
Purpose of this fictional discovery conversation.
Three observed orders
Supplied recordsupportedThe two mixed orders took ten minutes each. Food became ready after their drinks. The latte-only order took five minutes.
September 14, three orders only. Investigate food packing; this sample does not establish a permanent bottleneck.
Name the concept
Conceptual model: A purpose-driven representation of the important concepts and connections. A domain/logical view adds rules and detail; an instantiated view shows particular examples.
Relationship: A named connection between things, such as Person places Order.
Event / transaction: An event is an occurrence, such as Order Placed. A transaction records an agreed unit of activity; its boundary and completion need a definition.