@thanh01.pmt/curriculum-kit 1.4.41 → 1.4.43

package/docs/refs/templates/LESSONS_LEARNED_template.md

@@ -0,0 +1,49 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "LESSONS_LEARNED"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "{{DELIVERABLE_CODE}}"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# PROJECT LESSONS LEARNED
+
+_Rule: This file MUST be uploaded to NotebookLM NB-4 (Institutional Memory) after the Handover._
+
+## 1. Project Metadata
+- **Course Name:** [Name]
+- **Client / Audience:** [Client Name / Student Age]
+- **Deployment Period:** [Start Date] ➔ [End Date]
+- **Key Performance Metrics:**
+  - Total Lessons: [X]
+  - Average Revision Count (ARC) per lesson: [Y] (Target < 1.5)
+  - Severe Errors (Escalations): [Z]
+
+---
+
+## 2. What Worked Well (Successes)
+_Record formats, examples, or workflows that were highly effective for future reuse. MUST be specific._
+- [E.g., Using the 5E model for Circuitry helped Grade 5 students discover LED connections more intuitively than a theory-first lecture.]
+- [E.g., Batching Metered Execution into 2-lesson sets allowed for early tone correction, saving 40% of revision time.]
+
+## 3. What Didn't Work (Failures/Bottlenecks)
+_Record bottlenecks and reasons for failure. Avoid vague statements._
+- [E.g., The RUBRIC template was too complex for Elementary students; they couldn't use it for self-assessment.]
+- [E.g., @activity frequently proposed components not available in the Learner Profile due to lack of cross-checking.]
+
+## 4. Key Design Decisions (Architecture Log)
+_Record the "WHY" behind critical architecture choices to prevent future questioning of established patterns._
+- [E.g., Chose Arduino Uno over micro:bit because the client's budget was strictly $5/kit, despite micro:bit being easier to teach.]
+- [E.g., Moved the Python Programming module to the end of the course because students needed to master logic via Scratch drag-and-drop first.]
+
+## 5. Actionable Improvements for Future Projects
+_SPECIFIC actions to update the Curriculum OS._
+- **Template Updates:** [E.g., Need to simplify `RUBRIC_template.md` for Elementary audiences.]
+- **Rule Updates:** [E.g., Add a rule forcing `@activity` to re-read the component list in `CONTENT_CONTINUITY` before starting a new lesson.]
+
+## 6. Open Questions / Post-Deployment Monitoring
+_Uncertainties requiring follow-up after a few months of client operation._
+- [E.g., Is the 90-minute duration too long for Grade 3 attention spans? Need to check with teachers after 2 months.]

package/docs/refs/templates/LESSON_5E_template.md

@@ -0,0 +1,127 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "LESSON_5E"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T1"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+prerequisite: []
+template_contract: "lesson-plan-v2"
+template_required_sections:
+  - "A. Lesson Design Plan"
+  - "Learning Objectives & Evidence"
+  - "Activity Sequence"
+  - "Resource Map"
+  - "Assessment Map"
+  - "Artifact Contract"
+  - "B. Lesson Flow"
+  - "Artifact Linkage"
+---
+<!-- INJECT_BODY -->
+
+# LESSON [XX]: [LESSON TITLE] (5E Model)
+
+## [REQUIRED] A. Lesson Design Plan
+
+> OWNERSHIP: Each fact lives in exactly ONE section. The Artifact Contract
+> column (row 11) of the Activity Sequence is the single owner of which
+> satellite produces what. Resource Map lists ONLY physical/logistical
+> resources (hardware, accounts, printed material) — do not re-list satellite
+> artifacts there. Artifact Contract (§5) and Artifact Linkage name satellites
+> by filename + one-line role, no repeated descriptions. Lesson Flow
+> references activities by Seq number — never embed question banks or
+> self-check text owned by KX/QUIZ.
+
+### 1. Learning Objectives & Evidence
+- **Estimated Duration:** [X minutes]
+- **Materials & Equipment:** [List hardware and software]
+- **Keywords / Core Concepts:** [Keyword 1], [Keyword 2]
+
+| LO | Objective (Bloom's) | Student Evidence | Success Criteria |
+|---|---|---|---|
+| LO1 | **[Bloom Verb]** [Content] | [Observable output/action] | [Measurable condition] |
+| LO2 | **[Bloom Verb]** [Content] | [Observable output/action] | [Measurable condition] |
+
+### 2. Activity Sequence
+> This is the canonical activity contract. Satellite artifacts must expand this sequence and must not invent a different one.
+
+| Seq | 5E Phase | Activity Type | Actor | Purpose | Student Action | Teacher Move | Output/Evidence | LO | Time | Artifact Contract |
+|---|---|---|---|---|---|---|---|---|---|---|
+| 1 | Engage | Hook / Discussion | Teacher + Students | [Why this opens the lesson] | [What students do] | [Prompt/facilitation move] | [Evidence/checkpoint] | LO1 | [X mins] | SLIDE/HANDOUT |
+| 2 | Explore | Exploration / Demo | Students | [What students discover] | [What students try/observe] | [How teacher guides without overexplaining] | [Evidence/checkpoint] | LO1 | [X mins] | ACT/WKS |
+| 3 | Explain | Mini Lesson | Teacher + Students | [Concept to formalize] | [What students annotate/answer] | [Explanation/demo] | [Evidence/checkpoint] | LO1, LO2 | [X mins] | SLIDE/HANDOUT |
+| 4 | Elaborate | Practice / Lab | Students | [Main application] | [What students build/solve] | [Coaching/debugging] | [Main evidence] | LO2 | [X mins] | ACT/CODE_LAB/WKS |
+| 5 | Evaluate | Reflection / Check | Students | [Mastery check] | [Exit response/demo] | [Debrief] | [Assessment evidence] | LO1, LO2 | [X mins] | QUIZ |
+
+### 3. Resource Map
+| Resource | Used In Activity | Purpose | Owner Artifact |
+|---|---|---|---|
+| [Slide / handout / code template / hardware] | [Seq #] | [Why needed] | [SLIDE/HANDOUT/ACT/CODE_LAB/BOM] |
+
+### 4. Assessment Map
+| Evidence | Assessed By | Criteria | Follow-up If Missing |
+|---|---|---|---|
+| [Student output] | [Exit ticket / rubric / quiz item] | [Criteria] | [Reteach/retry action] |
+
+### 5. Artifact Contract
+- **ACT must expand:** [Seq numbers and details to operationalize]
+- **GUIDE must support:** [Teacher moves and facilitation risks from the activity sequence]
+- **SLIDE must visualize:** [Key concepts, checkpoints, and transitions]
+- **HANDOUT must provide:** [Student-facing reference needed during activities]
+- **WKS must practice:** [Skills/evidence from the sequence]
+- **QUIZ must assess:** [LO evidence and success criteria]
+- **EXT must extend:** [Main evidence target without changing core LO]
+
+---
+
+## [REQUIRED] B. Lesson Flow
+
+### 1. ENGAGE — [X mins]
+- **Hook Scenario:** [Provide a detailed real-world situation or story to grab attention. E.g., "Roleplay as a server room engineer at 3 AM."]
+- **Open Question:** [Explicitly state the question the teacher will ask the class.]
+- **Transition:** [How the teacher summarizes to move to the Explore phase.]
+
+### 2. EXPLORE — [X mins]
+- **Activity Reference:** [Summarize the planned activity from the Activity Sequence. Detailed operation belongs in ACT, but the design decision lives here.]
+- **Student Discovery:** [What students should notice before formal explanation.]
+
+### 3. EXPLAIN — [X mins]
+- **Definitions:** [Explain the core concepts.]
+- **Visual Illustration (REQUIRED):** [MUST include a specific example of data, code, JSON payload, or a Mermaid diagram to visualize the concept. No abstract-only explanations.]
+
+### 4. ELABORATE — [X mins]
+- **Tiered Scaffolding:**
+  - 🥉 **Bronze:** [Overview of the foundational task]
+  - 🥈 **Silver:** [Overview of the application task]
+  - 🥇 **Gold:** [Overview of the extension task]
+
+> **ACT Contract**: Detailed operational instructions must expand the Activity Sequence above and must not change the planned evidence target.
+
+### 5. EVALUATE — [X mins]
+- **Exit Ticket:** [Provide 1-2 specific questions to quickly check mastery of the success criteria.]
+- **Closing:** [Final remarks and wrap-up notes.]
+
+> **QUIZ Contract**: Detailed assessment criteria and rubrics must assess the evidence and success criteria defined in the Lesson Design Plan.
+
+---
+
+## [OPTIONAL] Teacher Notes
+- **Common Pitfalls:** [Where students often struggle.]
+- **Troubleshooting:** [Fast fixes for common errors.]
+
+---
+
+## [REQUIRED] Artifact Linkage (Master Index)
+> List all satellite files used in this lesson.
+
+| Artifact File | Role in the Classroom | When to Use |
+|---|---|---|
+| `GUIDE_...` | Detailed Teaching Script | Teacher preparation |
+| `SLIDE_...` | Presentation Content | Throughout the session |
+| `HANDOUT_...` | Theory Summary for Students | During EXPLAIN phase |
+| `ACT_...` | Detailed Learning Activity Operations | During EXPLORE / ELABORATE / checkpoint phases |
+| `WKS_...` | Individual Worksheet | Wrap-up or Homework |
+| `QUIZ_...` | Assessment Rubric | During EVALUATE phase |
+| `EXT_...` | Enrichment Materials | For "Gold" students |

package/docs/refs/templates/LESSON_EDP_template.md

@@ -0,0 +1,104 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "LESSON_EDP"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T1"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+prerequisite: []
+template_contract: "lesson-plan-v2"
+template_required_sections:
+  - "A. Lesson Design Plan"
+  - "Learning Objectives & Evidence"
+  - "Activity Sequence"
+  - "Resource Map"
+  - "Assessment Map"
+  - "Artifact Contract"
+  - "B. Lesson Flow"
+  - "Artifact Linkage"
+---
+
+# LESSON [XX]: [PROJECT TITLE] (EDP Model - Engineering Design Process)
+
+## [REQUIRED] A. Lesson Design Plan
+
+> OWNERSHIP: Each fact lives in exactly ONE section. The Artifact Contract
+> column of the Activity Sequence is the single owner of which satellite
+> produces what. Resource Map lists ONLY physical/logistical resources — do
+> not re-list satellite artifacts there. Lesson Flow references activities by
+> Seq number — never embed question banks or self-check text owned by KX/QUIZ.
+
+### 1. Learning Objectives & Evidence
+- **Estimated Duration:** [X minutes / X sessions]
+- **Project Objective:** [Describe the final product students will build]
+- **Materials & Equipment:** [Complete list of components]
+
+| LO | Objective (Bloom's / EDP) | Student Evidence | Success Criteria |
+|---|---|---|---|
+| LO1 | [Define / Imagine / Plan / Create / Test / Share] [Specific Content] | [Observable project artifact/action] | [Measurable condition] |
+| LO2 | [Define / Imagine / Plan / Create / Test / Share] [Specific Content] | [Observable project artifact/action] | [Measurable condition] |
+
+### 2. Activity Sequence
+> This is the canonical activity contract. Satellite artifacts must expand this sequence and must not invent a different one.
+
+| Seq | EDP Phase | Activity Type | Actor | Purpose | Student Action | Teacher Move | Output/Evidence | LO | Time | Artifact Contract |
+|---|---|---|---|---|---|---|---|---|---|---|
+| 1 | Ask | Problem Framing | Teacher + Students | [Clarify challenge] | [Students restate constraints] | [Present scenario/constraints] | [Problem statement] | LO1 | [X mins] | SLIDE/HANDOUT |
+| 2 | Imagine | Ideation | Students | [Generate options] | [Brainstorm/sketch] | [Facilitate comparisons] | [Idea list/sketches] | LO1 | [X mins] | WKS |
+| 3 | Plan | Design | Students | [Select solution path] | [Diagram/pseudocode/material plan] | [Review feasibility] | [Plan artifact] | LO1, LO2 | [X mins] | ACT/WKS |
+| 4 | Create | Build / Code | Students | [Build product] | [Assemble/code/test] | [Coach/debug] | [Working prototype] | LO2 | [X mins] | ACT/CODE_LAB/BOM |
+| 5 | Test & Improve | Iteration | Students | [Improve product] | [Record bugs/improvements] | [Prompt evidence-based fixes] | [Iteration log] | LO2 | [X mins] | WKS/QUIZ |
+| 6 | Share & Evaluate | Demo / Reflection | Students | [Communicate learning] | [Demo/explain] | [Debrief] | [Presentation/evaluation] | LO1, LO2 | [X mins] | QUIZ/EXT |
+
+### 3. Resource Map
+| Resource | Used In Activity | Purpose | Owner Artifact |
+|---|---|---|---|
+| [Slide / handout / code template / hardware] | [Seq #] | [Why needed] | [SLIDE/HANDOUT/ACT/CODE_LAB/BOM] |
+
+### 4. Assessment Map
+| Evidence | Assessed By | Criteria | Follow-up If Missing |
+|---|---|---|---|
+| [Student output] | [Rubric / demo / quiz item] | [Criteria] | [Reteach/retry action] |
+
+### 5. Artifact Contract
+- **ACT must expand:** [Seq numbers and details to operationalize]
+- **GUIDE must support:** [Teacher moves and facilitation risks from the activity sequence]
+- **SLIDE must visualize:** [Project challenge, constraints, checkpoints, and transitions]
+- **HANDOUT must provide:** [Student-facing reference needed during activities]
+- **WKS must practice/record:** [Planning, testing, or reflection evidence]
+- **QUIZ must assess:** [Project evidence and success criteria]
+- **EXT must extend:** [Main project evidence without changing core LO]
+
+---
+
+## [REQUIRED] B. Lesson Flow
+
+### 1. ASK (Define the Problem) — [X mins]
+[Set the context/story. What are the project requirements and constraints? (E.g., Build an obstacle-avoiding robot, budget under $10, use max 2 sensors).]
+
+### 2. IMAGINE (Ideate) — [X mins]
+[Students brainstorm possible solutions. Teacher suggests different approaches.]
+
+### 3. PLAN (Design) — [X mins]
+[Students draw circuit diagrams, create flowcharts, or write pseudocode before physical assembly.]
+
+### 4. CREATE (Build & Code) — [X mins]
+[Students start hardware assembly and typing code based on their design.]
+
+> **ACT Contract**: Detailed operational instructions must expand the Activity Sequence above and must not change the planned evidence target.
+
+### 5. TEST & IMPROVE (Iterate) — [X mins]
+[Students test their product, record bugs, and proceed with debugging/iteration.]
+
+### 6. SHARE & EVALUATE (Present) — [X mins]
+[Students demo their product, explain how it works, and highlight improvements made.]
+
+> **QUIZ Contract**: Detailed project rubrics must assess the evidence and success criteria defined in the Lesson Design Plan.
+
+---
+
+## [OPTIONAL] C. Teacher Facilitation Notes
+- **Project Bottlenecks:** [Where are students likely to get frustrated?]
+- **Extension for Fast Learners:** [Suggestions for upgrading features.]

package/docs/refs/templates/LESSON_GENERAL_template.md

@@ -0,0 +1,117 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "LESSON_GENERAL"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T1"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+prerequisite: []
+template_contract: "lesson-plan-v2"
+template_required_sections:
+  - "A. Lesson Design Plan"
+  - "Learning Objectives & Evidence"
+  - "Activity Sequence"
+  - "Resource Map"
+  - "Assessment Map"
+  - "Artifact Contract"
+  - "B. Lesson Flow"
+  - "Artifact Linkage"
+---
+<!-- INJECT_BODY -->
+
+# LESSON [XX]: [LESSON TITLE]
+
+## [REQUIRED] A. Lesson Design Plan
+
+> OWNERSHIP: Each fact lives in exactly ONE section. The Artifact Contract
+> column of the Activity Sequence is the single owner of which satellite
+> produces what. Resource Map lists ONLY physical/logistical resources — do
+> not re-list satellite artifacts there. Lesson Flow references activities by
+> Seq number — never embed question banks or self-check text owned by KX/QUIZ.
+
+### 1. Learning Objectives & Evidence
+- **Estimated Duration:** [X minutes]
+- **Materials & Equipment:** [List hardware, software, and instructional materials]
+- **Keywords / Core Concepts:** [Keyword 1], [Keyword 2]
+
+| LO | Objective (Bloom's) | Student Evidence | Success Criteria |
+|---|---|---|---|
+| LO1 | By the end of this lesson, students will be able to [Bloom Verb] [Specific Content]. | [Observable output/action] | [Measurable condition] |
+| LO2 | By the end of this lesson, students will be able to [Bloom Verb] [Specific Content]. | [Observable output/action] | [Measurable condition] |
+
+### 2. Activity Sequence
+> This is the canonical activity contract. Satellite artifacts must expand this sequence and must not invent a different one.
+
+| Seq | Lesson Stage | Activity Type | Actor | Purpose | Student Action | Teacher Move | Output/Evidence | LO | Time | Artifact Contract |
+|---|---|---|---|---|---|---|---|---|---|---|
+| 1 | Warm-up | Hook / Discussion | Teacher + Students | [Why this opens the lesson] | [What students do] | [Prompt/facilitation move] | [Evidence/checkpoint] | LO1 | [X mins] | SLIDE |
+| 2 | Core Concepts | Mini Lesson / Media Study | Teacher + Students | [Concept to establish] | [What students read/watch/annotate] | [Explanation/demo] | [Evidence/checkpoint] | LO1 | [X mins] | SLIDE/HANDOUT |
+| 3 | Guided Practice | Guided Demo / Practice | Teacher + Students | [Skill to model] | [What students attempt] | [Model/coaching move] | [Evidence/checkpoint] | LO2 | [X mins] | ACT/WKS |
+| 4 | Independent Practice | Practice / Lab | Students | [Main application] | [What students build/solve] | [Debug/coaching] | [Main evidence] | LO2 | [X mins] | ACT/CODE_LAB/WKS |
+| 5 | Wrap-up | Reflection / Check | Students | [Mastery check] | [Exit response/demo] | [Debrief] | [Assessment evidence] | LO1, LO2 | [X mins] | QUIZ |
+
+### 3. Resource Map
+| Resource | Used In Activity | Purpose | Owner Artifact |
+|---|---|---|---|
+| [Slide / handout / code template / hardware] | [Seq #] | [Why needed] | [SLIDE/HANDOUT/ACT/CODE_LAB/BOM] |
+
+### 4. Assessment Map
+| Evidence | Assessed By | Criteria | Follow-up If Missing |
+|---|---|---|---|
+| [Student output] | [Exit ticket / rubric / quiz item] | [Criteria] | [Reteach/retry action] |
+
+### 5. Artifact Contract
+- **ACT must expand:** [Seq numbers and details to operationalize]
+- **GUIDE must support:** [Teacher moves and facilitation risks from the activity sequence]
+- **SLIDE must visualize:** [Key concepts, checkpoints, and transitions]
+- **HANDOUT must provide:** [Student-facing reference needed during activities]
+- **WKS must practice:** [Skills/evidence from the sequence]
+- **QUIZ must assess:** [LO evidence and success criteria]
+- **EXT must extend:** [Main evidence target without changing core LO]
+
+---
+
+## [REQUIRED] B. Lesson Flow
+
+### 1. Warm-up / Hook — [X mins]
+[Inquiry-based question, short game, or story to grab attention, connecting to prior knowledge or real-world applications.]
+
+---
+
+### 2. Core Concepts — [X mins]
+
+### Concept 1: [Concept Name]
+[Explain theory in age-appropriate language. Use real-world analogies. Max 3 paragraphs.]
+- **Illustrative Example:** [Specific example]
+
+### Concept 2: [Concept Name] (if applicable)
+[Theory explanation]
+- **Illustrative Example:** [Specific example]
+
+---
+
+### 3. Guided Practice — [X mins]
+[Teacher demos or guides students step-by-step according to the Activity Sequence. Include code snippets, Mermaid diagrams, or basic wiring schematics.]
+
+---
+
+### 4. Independent Practice — [X mins]
+[Students solve a problem or challenge based on the planned evidence target.]
+
+> **ACT Contract**: Detailed operational instructions must expand the Activity Sequence above and must not change the planned evidence target.
+
+---
+
+### 5. Wrap-up & Checkpoint — [X mins]
+[Summarize the 2-3 most important points. Provide 2-3 quick check questions to ensure understanding before class ends.]
+
+> **QUIZ Contract**: Detailed assessment criteria and rubrics must assess the evidence and success criteria defined in the Lesson Design Plan.
+
+---
+
+## [OPTIONAL] C. Teacher Notes
+- **Common Pitfalls:** [Where do students usually go wrong?]
+- **Troubleshooting:** [Fastest way to fix common circuit/code errors?]
+- **Extension Tasks:** [Enrichment questions or extra challenges for fast learners.]

package/docs/refs/templates/OUTPUT_CONSTRAINTS_template.md

@@ -0,0 +1,38 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "OUTPUT_CONSTRAINTS"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "{{DELIVERABLE_CODE}}"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# CONTENT GENERATION CONSTRAINTS
+
+_Strict rules for @content, @activity, and @assessor to ensure pedagogical quality._
+
+## 1. Structural Constraints
+- **Header Hierarchy:** Must strictly follow Markdown nesting (h1 ➔ h2 ➔ h3).
+- **Required Sections:** Every Lesson MUST have: Overview, Warm-up, Core Concepts, Guided Practice, Independent Practice, Wrap-up.
+- **Link Integrity:** All internal links to `ACT`, `QUIZ`, or `SLIDE` must use the standardized U-M-L pathing: `[Link text](file:///.../_content/UXX/LXX/TYPE_UXX_MXX_LXX.md)`.
+
+## 2. Quantitative Constraints
+- **Word Count:** Lesson Plan (800 - 1500 words), Student Handout (max 500 words).
+- **Paragraph Length:** Max 3 sentences per paragraph for readability.
+- **Bullet Points:** Use lists for sequences or feature sets; avoid "walls of text."
+
+## 3. Pedagogical Constraints
+- **Bloom's Alignment:** Objectives must use strong verbs (Identify, Describe, Build, Debug).
+- **Inquiry-First:** Activities should start with a "Why" or a "Problem" before the "How-to."
+- **Analogy Rule:** Every abstract concept (e.g., Cloud, API) MUST have at least one real-world analogy.
+
+## 4. Code & Technical Constraints
+- **Executable Code:** All code blocks must be self-contained or explicitly state dependencies.
+- **Comments:** Minimum 30% code-to-comment ratio for student examples.
+- **Circuit Safety:** Explicitly mention safety warnings (e.g., common grounds, polarity) for hardware projects.
+## 5. Language Constraints
+- **Structure (Headers):** All major section headings MUST be in English (e.g., `## [REQUIRED] 1. Overview`).
+- **Body Content:** All pedagogical explanations, instructions, and feedback MUST be authored in English by default (Plan C — English-canonical). The `language` parameter controls the localized output language; see /localize-course for translation.
+- **Bilingual Support:** Technical terms are written in English with the localized translation added during the localization step (e.g., `Sensor (<translation>)` — the translation column is produced by /localize-course, never authored).

package/docs/refs/templates/PACKAGING_SPEC_template.md

@@ -0,0 +1,56 @@
+---
+id: "UNIT_CODE-PACKAGING"
+title: "Packaging Spec: [PROJECT_NAME]"
+type: "PACKAGING_SPEC"
+created_by: "Antigravity"
+phase: "P3"
+deliverable: "P3-SPEC"
+version: "v2.0"
+date: "YYYY-MM-DD"
+---
+
+# PACKAGING & TRANSFORMATION SPECIFICATION
+
+_This spec defines how raw artifacts are transformed and packaged into the 4 final delivery packages._
+
+## 1. Package Structure & Rules
+
+| Package ID | Target Audience | Transformation Rules | Source Artifacts |
+|---|---|---|---|
+| **P-TCH** | Teacher | In-depth pedagogical language, full answers and teaching tips. | LESSON, ACT, QUIZ, SLIDE, GUIDE |
+| **P-STD** | Student | "I can..." language, teacher notes removed, includes worksheets. | LESSON (⚡), ACT, QUIZ (⚡), WKS, HANDOUT, EXT |
+| **P-PRN** | Parent | Non-technical language, focused on outcomes and applications. | LESSON (⚡), HANDOUT |
+| **P-CLT** | Client | Curriculum map, technical standards and BOM report. | FRAMEWORK, PROJECT_BRIEF, ALIGNMENT_MATRIX |
+
+## 2. Transformation Rules (⚡)
+
+### A. For Students (Student Version)
+- **Lesson objectives:** Convert from pedagogical terminology to student-centered language.
+  - *Source:* "Student can program a for loop." ➔ *Target:* "After this lesson, I can program a for loop."
+- **Content:** Remove all sections marked `## [OPTIONAL] Teacher Notes`.
+- **Assessment:** Convert complex rubric tables into simple self-assessment checklists for students.
+- **Answer keys:** Remove any line starting with `Answer:` or inside spoiler tags.
+
+### B. For Parents (Parent Version)
+- **Outcomes:** Translate technical skills into real-world achievements.
+  - *Source:* "Understand PWM mechanisms." ➔ *Target:* "Your child built a night light with adjustable brightness."
+- **Home interaction:** Provide open-ended questions for parents to discuss with their child about the finished product.
+
+### C. For Managers / Clients (Client Version)
+- **Standards:** Emphasize alignment with educational standard codes (CSTA, K12 CS, ITP).
+- **Assessment:** Show the method and completion criteria, omitting overly deep technical detail.
+
+## 3. Data Sanitization Protocol
+
+Before saving files to `_released/packages/`, **MANDATORY** scan and removal:
+
+1.  **YAML Frontmatter**: Remove the whole block between the `---` delimiters at the top of the file.
+2.  **Agent references**: Remove persona names (e.g. `@content`, `@reviewer`, `@analyst`).
+3.  **Internal tags**: Remove `[SME_MANDATE]`, `[FIXME]`, `[TODO]`, `[REQUIRED]` tags.
+4.  **Hidden comments**: Remove all HTML comments (`<!-- ... -->`).
+5.  **Revision labels**: Remove labels like `[TONE]`, `[DEPTH]`, `[SCOPE]`.
+6.  **System notes**: Remove notes intended only for the production process or Agent instructions.
+
+---
+- **Global Standard:** v4.6 (Packaging Core).
+- **Last Sync:** YYYY-MM-DD.

package/docs/refs/templates/PILOT_FEEDBACK_template.md

@@ -0,0 +1,49 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "PILOT_FEEDBACK"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "{{DELIVERABLE_CODE}}"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# PILOT TEACHING FEEDBACK
+_Date Recorded: [YYYY-MM-DD]_
+
+## 1. Session Information
+- **Course / Module:** [Course Name - Module X]
+- **Lesson:** [Lesson # - Title]
+- **Lead Teacher:** [Name]
+- **Observer:** [Name]
+- **Student Group / Class:** [Qty - Grade Level]
+
+---
+
+## 2. Structured Feedback by Lesson Phase
+_Note specific issues encountered. Severity: 🔴 Major (Affects LOs) / 🟡 Minor (Polish needed)._
+
+| Phase | Observed Issue / Difficulty | Severity | Suggested Revision |
+|---|---|:---:|---|
+| **Theory (Concept)** | [e.g., Variable explanation via gift boxes was confusing for students.] | [🔴/🟡] | [e.g., Change to labeled drawer analogy.] |
+| **Practice (Activity)** | [e.g., Not enough time for students to finish the circuit.] | [🔴/🟡] | [e.g., Remove one LED from the requirements.] |
+| **Assessment (Quiz)** | [e.g., Multiple choice question #2 was a trick question.] | [🔴/🟡] | [e.g., Rewrite question more directly.] |
+
+---
+
+## 3. General Observations
+- **Duration (Plan vs. Actual):** [X mins vs. Y mins]
+- **Practical Completion Rate:** [Approx. X% of students finished the product]
+- **Biggest Bottleneck:** [Which concept or step caused the most frustration?]
+- **Highlights (What worked well):** [Which part were students most engaged in?]
+
+---
+
+## 4. Overall Classification & Action (For System / Human PM)
+_Check [x] one of the boxes below for workflow routing:_
+
+- [ ] **🟡 MINOR / PATCH:** Stylistic errors, minor timing issues, weak examples.
+  👉 _Action:_ Forward to `@content` or `@activity` for direct revision on this lesson (Route to `/revise`).
+- [ ] **🔴 MAJOR:** Misaligned Learning Objectives (LOs), students completely unable to perform tasks, or fundamental technical errors.
+  👉 _Action:_ STOP pipeline. Requires Human and `@designer` to re-evaluate `CURRICULUM_FRAMEWORK.md` (Special Gate Triggered).

package/docs/refs/templates/PROJECT_BRIEF_template.md

@@ -0,0 +1,45 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "PROJECT_BRIEF"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P1-T9"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# PROJECT BRIEF: [PROJECT NAME]
+
+## 1. Project Overview
+- **Project Name:** [Full Name]
+- **Taxonomy:** `[PROJECT-CODE]`
+- **Core Objective:** [Briefly describe the core goal]
+
+## 2. Audience & Duration
+- **Learners:** [Age, proficiency level]
+- **Total Duration:** [Number of lessons/sessions]
+- **Environment:** [Online/Offline/Hybrid]
+
+## 3. Learning Roadmap
+- [Summary of the learning journey]
+
+## 4. Learning Outcomes & Deliverables
+- [Certificates / Projects achieved]
+
+## 5. Technical Constraints
+- [Tools, languages, hardware required]
+
+## 6. Artifact Scope
+| Artifact Type | Required? | Notes |
+|---|:---:|---|
+| LESSON | ✅ | Master Lesson Plan |
+| ACT | ✅ | Hands-on Activity Guide |
+| QUIZ | ✅ | Exit Ticket & Rubric |
+| SLIDE | ✅ | Presentation Slide Deck |
+| WKS | ✅ | Printed Worksheet |
+| EXT | ⬚ | Extension/Advanced Tasks |
+| GUIDE | ✅ | Teacher Script/Guide |
+| HANDOUT | ⬚ | Student Reference Material |
+| CODE | ✅ | Code files |
+| ASSET | ⬚ | Images/Illustrations |

package/docs/refs/templates/PROJECT_STATUS_template.md

@@ -0,0 +1,64 @@
+---
+id: "UNIT_CODE-STATUS"
+title: "Project Status: [PROJECT_NAME]"
+type: "PROJECT_STATUS"
+created_by: "Antigravity"
+phase: "P1"
+deliverable: "P1-GATE"
+version: "v4.6"
+date: "YYYY-MM-DD"
+---
+
+# PROJECT STATUS: [PROJECT_NAME]
+
+## 1. Project Summary
+- **Main Objective:** [Brief summary of the project objective]
+- **Current Phase:** P1 (Analysis & Research)
+- **Core Completion Rate (Core 3):** 0% (auto-updated)
+- **Full Pack Completion Rate (Required 8):** 0% (auto-updated)
+- **Status Label:** `🔵 INITIALIZED`
+
+## 2. Macro Pipeline (Course Lifecycle)
+| Phase | Stage | Responsibility | Status | Gate Status |
+| :--- | :--- | :--- | :--- | :--- |
+| **P1: R&D** | Research & Analysis | @analyst | 🔄 Running | ⏳ Gate 1 (Pending) |
+| **P2: Architecture** | Curriculum Framework | @designer | ⚪ Waiting | ⏳ Gate 2 (Pending) |
+| **P3: Production** | **Active: Unit XX** | @content | ⚪ Waiting | ⏳ Gate 3 (Pending) |
+| **P4: Delivery** | Packaging & Handover | @packager | ⚪ Waiting | ⏳ Gate 4 (Pending) |
+
+## 3. High-Level Roadmap
+- [ ] **Unit 01: [Title]** (⏳ Pending)
+- [ ] **Unit 02: [Title]** (⏳ Pending)
+- [ ] **Unit 03: [Title]** (⏳ Pending)
+
+## 4. Micro Pipeline (Active Production Flow - Unit [XX])
+| Step | Workflow Stage | Artifact Types | Progress | Status |
+| :--- | :--- | :--- | :--- | :--- |
+| **S1** | **Drafting** | LESSON | 0% | ⚪ PENDING |
+| **S2** | **Technical Lab** | ACT, CODE_LAB | 0% | ⚪ PENDING |
+| **S3** | **Assessment** | QUIZ, RUBRIC | 0% | ⚪ PENDING |
+| **S4** | **Courseware** | SLIDE, WKS, GUIDE | 0% | ⚪ PENDING |
+| **S5** | **Quality Control** | REVIEW, SME_AUDIT | 0% | ⚪ PENDING |
+
+## 5. Detailed Progress Tracking
+| Lesson | Title | Status | Artifacts | Last Action |
+| :--- | :--- | :--- | :--- | :--- |
+| **U01_M01_L01** | [Lesson Title] | ⚪ | 0/8 | Initialized |
+
+## 6. Critical Links
+- **Changelog (Full History):** [CHANGELOG.md](CHANGELOG.md)
+- **Asset Manifest:** [ASSET_MANIFEST.md](ASSET_MANIFEST.md)
+- **Alignment Matrix:** [ALIGNMENT_MATRIX.md](ALIGNMENT_MATRIX.md)
+
+## 7. Changelog (Latest Only)
+
+### 🎯 Current Milestone: Phase 1 - R&D
+- **Current Task:** [current task name]
+
+### 🚀 Active Sprint (Unit [XX])
+- [ ] [Task 1]
+- [ ] [Task 2]
+
+---
+- **Global Standard:** v4.6 (Operational-First).
+- **Last Sync:** YYYY-MM-DD HH:mm.