TinkerLoading Larkspur mini
Larkspur miniOrder 1042 under your schema: Team: list · Status: list · Days to arrive: number.
Chapter 7 of 7
Workbench: Larkspur’s order schema
Time to design the real thing: Larkspur’s order-status schema, for four orders, with what you know about masks, lists, room and what the model can know.
This chapter: Which schema gets a valid and right answer for every order?
You will learn
- How to choose, field by field, between free text, a list and leaving it to the system
- Why the model should only fill what it can know
- How to read validity and correctness side by side
Words you’ll meet (1)
- Order system
- Larkspur’s database of orders. It knows each order’s status and days to arrive; the model doesn’t.
The picture on the left is live. Each step below asks you to do one thing in it; the story continues here as you go.
Step 1 of 3
Larkspur’s order-status answer has three fields: the team that handles it, the status, and the days to arrive. Here are 4 real orders; the order system knows each one’s status and days, but not which team handles it. The team’s first draft asks the model for everything. Before you run it: