🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Source: 00C canonical Google Doc. This page preserves the execution-card content while GitHub provides navigation.
Sequence 003 - Read the source-fidelity rules before content
Program Orientation | Orientation
| WHEN / PURPOSE — Prevent general web knowledge or tool behavior from silently replacing DAMA meaning. |
|---|
WHAT YOU SHOULD LEARN
- The current DMBOK chapter PDF controls DAMA-specific meaning.
- The curriculum map predicts lab type but cannot invent chapter rules.
- Technology documentation controls software behavior, not DMBOK meaning.
- Missing chapter artifacts are build gates, not permission to improvise.
WHAT TO READ / STUDY
| Priority | Resource | Open | Use now | Stop point |
|---|---|---|---|---|
| MUST | Main 00A control guide | OPEN | Review source-fidelity and Q&A rules. | Do not begin Chapter 2+ mastery artifacts from memory. |
| MUST | Applied Lab Curriculum Map | OPEN | Understand that lab plans are source-gated. | Do not treat the map as DMBOK text. |
DO THIS IN ORDER
- Write the authority hierarchy in your own words.
- Mark DMBOK chapter PDF as the source of DAMA-specific terminology.
- Mark vendor docs as implementation sources only.
- Define what happens when an artifact is missing.
MERIDIAN APPLICATION
This keeps Meridian exercises faithful to the chapter rather than becoming generic “data best practices.”
STOP / BOUNDARY: Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth.
CREATE / SAVE
Authority hierarchy note.
YOU ARE DONE WHEN: You can identify which source wins in three conflict examples.
NEXT → Sequence 004
🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →