Task 01 Data Structure Alignment Lab Guide
📥 Lab input
- •
day3_meeting_notes.md(meeting notes)
💾 Lab output
- •
erd-schema.md(data spec and ERD)
1. Story and lab background
A startup's planning room. The planner kindly explained the flow: "When a user views an expert's profile and books, the expert can approve or reject, and the booking is confirmed after payment." The planner thought of this as one simple screen flow.
But the developer pictured Users, Experts, Reservations and Payments tables, imagining a complex relational model: are they 1:N or N:M, and how do status values (Pending, Approved, Paid) interact? When planners and developers understand the same service policy differently like this, things get missed in database design, easily leading to runtime errors or data mismatches on screen.
In this lab, you'll learn to use Codex to clearly derive entities and relationships from planning meeting notes written in natural language, and structure them so both groups understand one matching design data model (ERD) without errors.
2. Learning goals
- Logically derive key entities (Entity) from unstructured meeting notes and screen flow descriptions.
- Clearly define relationships (Relation) and cardinality (1:1, 1:N, N:M) between entities.
- Turn the derived relational data structure into a Mermaid ERD and detailed table spec.
- Close the concept design gap (Data Alignment) between planners and developers.
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day3_meeting_notes.mdin theautomation/folder. - Hand the review to Codex: send the **Codex request prompt** below in the Codex Client prompt box and build.
- Check the relational model: review whether the 1:N and 1:1 relationships between User, Expert, Reservation and Payment, plus primary keys (PK) and foreign keys (FK), are defined as intended.
Download lab materials
Codex request prompt
Task 01 Prompt
Analyze the provided meeting notes from a data structure view, derive the key entities and relationships, and write a data structure doc and Mermaid ERD code.
4. Example output
Codex analyzes the meeting notes and outputs a normalized data entity mapping and Mermaid ERD script like below.
| Entity | Explanation | Main attributes | Relationships |
|---|---|---|---|
| User | Regular member who uses the consultation service | user_id (PK), email, nickname | 1:N with Reservation |
| Expert | Partner expert who gives consultations | expert_id (PK), name, category | 1:N with Reservation |
| Reservation | Booking mapping between user and expert | reservation_id (PK), user_id (FK), expert_id (FK), status | N:1 with User/Expert, 1:1 with Payment |
| Payment | Payment transaction info to confirm the booking | payment_id (PK), reservation_id (FK), amount, status | 1:1 with Reservation |
5. AI use points
- Entity reasoning: turns nouns that become data storage units (attributes) and action verbs into relationships in the description text.
- Mermaid schema build: automatically builds code for visuals, making teamwork easier to read.