🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Sequence 306 — CAP-04 Product / Reference Definition Split
Context: Cross-Chapter Integration & Capstones | Capstone / Integration
Source: CDMP Master Execution Manual
When / purpose
Integrate reference/master data, governance and metadata around inconsistent business meaning.
What you should learn
- Reference codes vs master entities.
- Definition ownership.
- Change control.
- Downstream impact.
What to read / study
| Priority | Resource | Use now | Stop point |
|---|---|---|---|
| MUST | Cross-Chapter Capstone & Incident Roadmap | Use only the capstone/checkpoint named by this card. | Do not pull future chapter controls into earlier checkpoints. |
| REFERENCE | Meridian Casebook | Use canonical systems/roles/incidents. | No new company facts without documenting them. |
Do this in order
- Read CAP-04.
- Locate competing definitions/codes.
- Trace impacted assets/reports.
- Propose authoritative decision and controlled change.
Meridian application
Reuse the actual Meridian artifacts created in prior chapters; the capstone should integrate, not restart.
Create / save
CAP-04 decision/change packet.
Stop / boundary
Use only chapters already completed at this point. Do not solve the incident with knowledge from future chapters.
Completion gate
You can explain how the definition is governed and propagated without silently overwriting history.
NEXT → Sequence 307
Operationalized from the verified canonical 00C Master Execution Manual; not a verbatim transcription. Separate chapter mastery packages and applied labs are not created by this migration.