---
id: "{{ID}}"
title: "{{TITLE}}"
type: "DEPENDENCY_MAP"
created_by: "Curriculum OS Builder"
phase: "{{PHASE}}"
deliverable: "{{DELIVERABLE_CODE}}"
version: "{{VERSION}}"
date: "{{DATE}}"
template_contract: "artifact-template-v1"
template_required_sections:
  - "Document Dependency Hierarchy"
  - "Cascade Impact Rules"
  - "Cascade Processing Protocol"
---
# CURRICULUM DEPENDENCY MAP: {{PROJECT_NAME}}

_Tracks the logical flow and technical prerequisites between units and lessons to prevent fragmentation._

## Document Dependency Hierarchy
Data flows top-down. An arrow `└──` means the document below MUST read the document above before it is produced.

```text
LEARNER_PROFILE.md (Source: Client)
 └── CURRICULUM_FRAMEWORK.md (reads Profile to design)
      ├── ART_DIRECTION.md (reads Profile & Framework)
      ├── CONTENT_STYLE_GUIDE.md (reads Profile & Framework)
      ├── _content/U[XX]/L[YY]/ (lesson folders containing the artifacts)
      │    ├── LESSON_U[XX]_M[ZZ]_L[YY].md (detailed lesson plan - reads Framework & Style Guide)
      │    ├── ACT_U[XX]_M[ZZ]_L[YY].md (hands-on activity - reads Lesson)
      │    └── QUIZ_U[XX]_M[ZZ]_L[YY].md (question bank & rubrics - reads Lesson & Framework)
      │          └── CONTENT_CONTINUITY.md (registers terminology & seamless pedagogy)
      └── ALIGNMENT_MATRIX.md (cross-checks and truth-syncs the whole system)
            └── PACKAGES (final deliverables: Teacher, Student, Parent, Client)
```

## Cascade Impact Rules
When a Scope Change request or Version update occurs, `@reviewer` MUST cross-check the table below to identify the affected files:

| If this file changes MAJOR/MINOR... | ...then these files MUST be Reviewed/Rewritten |
|---|---|
| **LEARNER_PROFILE** | Everything (Framework, Lessons, Activities, Quizzes). Usually requires a restart (special gate). |
| **CURRICULUM_FRAMEWORK** | Lessons (`LESSON_U[XX]_M[ZZ]_L[YY]`) of the changed module, `ACT_U[XX]_M[ZZ]_L[YY]`, `QUIZ_U[XX]_M[ZZ]_L[YY]`, `ALIGNMENT_MATRIX`. |
| **CONTENT_STYLE_GUIDE** | All `LESSON_U[XX]_M[ZZ]_L[YY]` (only Tone/Style revision, no structure change), `CONTENT_CONTINUITY`. |
| **ART_DIRECTION** | Regenerate the illustrations or circuit diagram designs affected by the new Style. |
| **LESSON_U[XX]_M[ZZ]_L[YY] (Theory)**| `ACT_U[XX]_M[ZZ]_L[YY]` (materials may change), `QUIZ_U[XX]_M[ZZ]_L[YY]` (criteria may change), `ALIGNMENT_MATRIX`. |
| **ACT_U[XX]_M[ZZ]_L[YY] (Hands-on)** | `QUIZ_U[XX]_M[ZZ]_L[YY]` (practical product assessment criteria may change). |

## Cascade Processing Protocol
1. Identify the original file that changed.
2. Follow the "Propagation Rules" above to list the affected files.
3. Build the **Cascade Impact Map** table into `PROJECT_STATUS.md` (Open Issues section) and mark 🔴 (needs rewrite) or 🟡 (needs review).
4. Assign `@content`, `@activity`, `@assessor` to process in top-down order of the dependency diagram.

## [OPTIONAL] Tool & Platform Dependencies
| Component | Minimum Version | Required For |
|---|---|---|
| Arduino IDE | 2.0+ | All hardware projects |
| Python | 3.10+ | AI and Data units |
| n8n | 1.0+ | Automation units |

---
- **Global Standard:** v4.6 (Operational-First).
- **Status:** ALIGNED TEMPLATE (Modular-First Architecture Alignment).