🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Source: 00C canonical Google Doc. This page preserves the execution-card content while GitHub provides navigation.
Sequence 009 - Understand build gates for Chapters 2–17
Program Orientation | Orientation
| WHEN / PURPOSE — Know how to proceed when the execution manual reaches a chapter whose mastery package or Meridian lab is not built yet. |
|---|
WHAT YOU SHOULD LEARN
- A missing chapter package is a controlled stop.
- The full chapter PDF must be read before the package is authored.
- The applied lab is finalized only after the chapter is source-checked.
- The execution manual may define the type of work without inventing DAMA-specific content.
WHAT TO READ / STUDY
| Priority | Resource | Open | Use now | Stop point |
|---|---|---|---|---|
| MUST | Main 00A chapter folders | OPEN | Confirm all 17 source PDFs exist. | Do not create content from memory. |
| MUST | Applied Chapter Labs container | OPEN | See reserved lab destinations. | Empty future lab folders are planned destinations. |
DO THIS IN ORDER
- Write the build-gate rule.
- When a later chapter is reached, verify the mastery package exists.
- If missing, have it built from the controlling chapter PDF.
- Then source-check/build the corresponding Meridian lab before continuing.
MERIDIAN APPLICATION
This prevents the guide from looking complete by hiding invented content inside future chapters.
STOP / BOUNDARY: Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth.
CREATE / SAVE
Build-gate rule in notes.
YOU ARE DONE WHEN: You know exactly what to do when the next required artifact is missing.
NEXT → Sequence 010
🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →