🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Source: 00C canonical Google Doc. This page preserves the execution-card content while GitHub provides navigation.
Sequence 004 - Meet Meridian Commerce Group at orientation depth
Program Orientation | Orientation
| WHEN / PURPOSE — Create enough company context to make later examples meaningful without memorizing the whole casebook. |
|---|
WHAT YOU SHOULD LEARN
- Meridian is a fictional omnichannel retailer.
- The same company persists through all chapters.
- Systems, domains, roles and defects are intentionally reusable.
- Synthetic data is evidence, not a substitute for business reasoning.
WHAT TO READ / STUDY
| Priority | Resource | Open | Use now | Stop point |
|---|---|---|---|---|
| MUST | Meridian Casebook | OPEN | Read company foundation, processes, systems, domains, personas and messy conditions. | Stop before memorizing every incident. |
| SHOULD | Synthetic Data Blueprint | OPEN | Skim dataset names and defect philosophy. | Do not start data tooling yet. |
DO THIS IN ORDER
- Write what Meridian sells and how customers interact with it.
- Name five major data domains.
- Name five systems.
- Name three existing data-management problems.
- Explain why one persistent company is better than unrelated exercises.
MERIDIAN APPLICATION
Your mental model should connect business processes → systems → data domains → governance problems.
STOP / BOUNDARY: Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth.
CREATE / SAVE
Meridian orientation note.
YOU ARE DONE WHEN: You can explain Meridian for 2–3 minutes without the casebook.
NEXT → Sequence 005
🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →