@thanh01.pmt/curriculum-kit 1.4.40 → 1.4.42

package/docs/refs/templates/ACT_template.md

@@ -0,0 +1,58 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "ACT"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T2"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+template_contract: "artifact-template-v1"
+template_required_sections:
+  - "Computational Thinking Focus"
+  - "Materials & Setup"
+  - "Constraints & Safety"
+  - "Active Learning Workflow"
+  - "3-Tier Differentiation"
+  - "Reflection"
+---
+<!-- INJECT_BODY -->
+
+# INQUIRY-BASED ACTIVITY: [ACTIVITY TITLE]
+_Unit: U[X] | Module: M[X.X] | Lesson: Lesson [XX]_
+
+## [REQUIRED] Computational Thinking Focus
+- **Problem Statement (Real-world Scenario):** [Describe a real problem instead of just assembly steps. E.g., "A farm weather station needs to alert when the temperature is too high."]
+- **Decomposition:** [E.g., 1. Read sensor, 2. Process logic, 3. Send alert.]
+- **Algorithm Design:** [How should students think about the Data Flow before programming?]
+
+## [REQUIRED] Materials & Setup
+- **Reference Material:** Students should use the **HANDOUT** for this lesson as their primary technical reference (lifeline).
+- **Hardware/Software:** [List specific devices, components, and tools required.]
+
+## [REQUIRED] Constraints & Safety
+- ⚠️ **Technical/Safety:** [E.g., Careful with 5V/GND pins, API rate limits.]
+- 💡 **Design Constraint:** [Provide a constraint to stimulate thinking. E.g., "Maximum 3 nodes allowed", "Environment variables MUST be used."]
+
+## [REQUIRED] Active Learning Workflow
+
+### Phase 1: Planning & Design — [X mins]
+- **Student Task:** Hand-draw (or draft in words) the algorithm flowchart or connection architecture before touching the computer/devices.
+- **Teacher Action:** Walk around to check the logic of each group. Ask inquiry questions: *"Where does the data flow from and to?", "If the sensor fails, how will the system report the error?"*
+
+### Phase 2: Implementation & Discovery — [Y mins]
+- **Student Task:** Apply the knowledge from the **HANDOUT** to realize the plan designed in Phase 1. Encourage self-inquiry and documentation lookup.
+- **Teacher Action:** Avoid "hand-holding." Only intervene if a group has been stuck for more than 5 minutes.
+
+### Phase 3: Debugging & Testing — [Z mins]
+- **Testing:** Students run their system.
+- **Error Analysis:** Ask students to record any error codes or unexpected behaviors and compare them with the Troubleshooting table in the Handout.
+
+## [REQUIRED] 3-Tier Differentiation
+> MUST design tasks in 3 tiers to support diverse learner groups. Bronze is the minimum requirement for all students.
+- 🥉 **Bronze (Foundational):** [Core task, usually corresponding to accurately completing the basics from the Handout. E.g., Calling an API and printing the result.]
+- 🥈 **Silver (Application):** [Task with additional logic or processing steps. E.g., Adding an IF Node to check if temperature > 30.]
+- 🥇 **Gold (Enrichment/Creative):** [Challenging task requiring self-research of new tools or advanced knowledge. E.g., Sending the alert via Telegram.]
+
+## [REQUIRED] Reflection
+- **Discussion Question:** [E.g., Why is Approach A better than B? Which part of the code runs the slowest?]

package/docs/refs/templates/ALIGNMENT_MATRIX_template.md

@@ -0,0 +1,45 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "ALIGNMENT_MATRIX"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T9"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# ALIGNMENT MATRIX
+_Updated by: @reviewer | Read by: All Agents_
+_Rule: @packager is ONLY allowed to publish materials when the Status column is all ✅._
+
+## 1. Vertical Alignment Tracker
+_Mapping: Objective (from Framework) ➔ Content ➔ Practice ➔ Assessment._
+_Note: This is the minimum structure (LESSON + ACT + QUIZ). Depending on the **Artifact Scope** defined in PROJECT_BRIEF.md, agents should add columns for other artifacts (SLIDE, WKS, EXT, GUIDE, HANDOUT)._
+
+| Unit/Lesson | Learning Objective | LESSON | ACT | QUIZ | STATUS |
+| :--- | :--- | :---: | :---: | :---: | :---: |
+
+*(Agent @reviewer automatically adds new rows when a lesson is successfully merged).*
+
+## 2. Horizontal & Prerequisite Alignment Report
+_Tracks logical errors, knowledge gaps, or redundancies between lessons._
+
+- **Knowledge Gaps:**
+  - [Date] - [Empty] *(Note if a future lesson uses concepts not yet taught)*
+- **Overlaps:**
+  - [Date] - [Empty] *(Note if two consecutive lessons re-teach the same concept > 40%)*
+
+## 3. Feedback & Revision Log
+_Where @reviewer records Feedback Labels for @content, @activity, or @assessor to implement changes._
+
+| Date | Lesson | Feedback Label | Issue Details | Assigned To | Revision Status |
+|---|---|---|---|---|:---:|
+| [Date] | [U01_M01_L04] | `[ALIGNMENT]` | [e.g., Objective is 'Creative' but task is only 'Follow Example'] | `@activity` | `[PENDING / RESOLVED]` |
+| ... | ... | ... | ... | ... | ... |
+
+---
+**Status Key:**
+- ✅ **Aligned:** Objective has matching theory + practice + assessment that are consistent.
+- ⚠️ **Partial:** Mentioned but misaligned, lacking depth, or missing one component.
+- ❌ **Missing:** Objective not taught or completely deviated from the framework.

package/docs/refs/templates/ART_DIRECTION_template.md

@@ -0,0 +1,43 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "ART_DIRECTION"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P2-T2"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# ART DIRECTION: [Project Name]
+
+## 🎨 1. Visual Identity & Mood
+- **Concept:** [Core metaphor or theme, e.g., "Cyber-punk Laboratory"]
+- **Aesthetic:** [Visual style, e.g., "Minimalist, high-contrast, flat design"]
+- **Mood:** [Keywords: e.g., Modern, Professional, Playful, Precise]
+
+## 🌈 2. Color Palette
+| Category | Hex Code | Purpose |
+|---|---|---|
+| **Primary** | `#XXXXXX` | Main background or UI elements. |
+| **Secondary**| `#XXXXXX` | Supporting colors for containers/borders. |
+| **Accent** | `#XXXXXX` | Call-to-action, highlights, or key information. |
+| **Text** | `#XXXXXX` | Primary typography color. |
+
+## 📊 3. Diagram Standards (Mermaid)
+- **Theme:** [Dark / Neutral / Default]
+- **Flowcharts:** Use `graph TD` with specific node styles.
+- **Circuitry:** [Standard for hardware diagrams, e.g., Fritzing style or SVG]
+
+## 🖼️ 4. Image Categories & Tiers
+1. **Tier 1 (Core):** [High-fidelity, AI-generated, or professional stock]
+2. **Tier 2 (Process):** [Clean vector diagrams or technical flowcharts]
+3. **Tier 3 (Reference):** [Real-world photos or hardware screenshots]
+
+## 🛠️ 5. Typography
+- **Headings:** [Font Family, e.g., "Outfit", "Inter"]
+- **Body:** [Font Family, e.g., "Roboto", "Open Sans"]
+
+---
+- **Global Standard:** v2.2 (Creative Core).
+- **Last Sync:** YYYY-MM-DD.

package/docs/refs/templates/ASSET_MANIFEST_template.md

@@ -0,0 +1,27 @@
+---
+id: "UNIT_CODE-ASSET-MANIFEST"
+title: "Asset Manifest: [PROJECT_NAME]"
+type: "ASSET_MANIFEST"
+created_by: "Antigravity"
+version: "v4.6"
+date: "YYYY-MM-DD"
+---
+
+# 📦 ASSET MANIFEST
+_Auto-updated by Radar at: YYYY-MM-DD HH:MM:SS | Learning-asset sync status_
+
+## 1. Summary
+- **Total referenced assets:** 0
+- **Ready (physical exists):** 0
+- **Missing (physically absent):** 0
+- **Readiness rate:** 0%
+
+## 2. Referenced Assets
+| File name | Referenced at | Asset type | Status | Physical path |
+|---|---|---|---|---|
+
+## 3. Orphan Assets
+_Files inside _assets that are not embedded in any lesson._
+
+| File name | Asset type | Physical path |
+|---|---|---|

package/docs/refs/templates/BASELINE_STANDARD.md

@@ -0,0 +1,37 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "BASELINE_STANDARD"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "{{DELIVERABLE_CODE}}"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# BASELINE STANDARDS (K-12 CS & AI)
+
+_Reference standards used for aligning Learning Objectives across the Curriculum OS._
+
+## 1. CSTA K-12 Computer Science Standards
+- **Level 1B (Grades 3-5):**
+  - [1B-AP-10] Create programs that include sequences, events, loops, and conditionals.
+  - [1B-AP-11] Decompose (break down) problems into smaller, manageable subproblems.
+- **Level 2 (Grades 6-8):**
+  - [2-AP-11] Create clearly named variables that represent different data types and perform operations on their values.
+  - [2-AP-12] Design and iteratively develop programs that combine control structures, including nested loops and compound conditionals.
+
+## 2. AI4K12 - Five Big Ideas in AI
+1. **Perception:** Computers perceive the world using sensors.
+2. **Representation & Reasoning:** Agents maintain representations of the world and use them for reasoning.
+3. **Learning:** Computers can learn from data.
+4. **Natural Interaction:** Intelligent agents require many kinds of knowledge to interact naturally with humans.
+5. **Societal Impact:** AI can impact society in both positive and negative ways.
+
+## 3. Bloom's Taxonomy for CS/STEM
+- **Remembering:** Recall basic coding syntax or hardware names.
+- **Understanding:** Explain how a loop or sensor works using analogies.
+- **Applying:** Use a known code structure to solve a similar problem.
+- **Analyzing:** Debug a circuit or code block by identifying logical errors.
+- **Evaluating:** Critically assess whether Approach A is more efficient than Approach B.
+- **Creating:** Design and build an original project from scratch (EDP model).

package/docs/refs/templates/BELL_RINGER_template.md

@@ -0,0 +1,108 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "BELL_RINGER"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T16"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+template_contract: "artifact-template-v1"
+template_required_sections:
+  - "Weekly Objective & Schedule"
+  - "Monday: Mental Model Recall (Warm-up 1)"
+  - "Tuesday: Code Spot-Check (Warm-up 2)"
+  - "Wednesday: Bug Hunt & Fix (Warm-up 3)"
+  - "Thursday: Architecture Tracing (Warm-up 4)"
+  - "Friday: Creative Synthesis & Bridge (Warm-up 5)"
+  - "Answer Key & Scoring Guide"
+---
+<!-- INJECT_BODY -->
+
+# WEEKLY BELL RINGERS (5-DAY WARM-UP PACK): [UNIT / LESSON TITLE]
+_Unit: U[X] | Module: M[X.X] | Time: Exactly 3-5 Mins at Start of Each Session_
+
+## [REQUIRED] Weekly Objective & Schedule
+- **Weekly Core Theme:** [E.g., "Swift Concurrency, Actors & Thread Safety"]
+- **Routine Protocol:** Display prompt on projector immediately as students enter. Students write responses in their Daily Journal before class discussion.
+
+---
+
+## [REQUIRED] Day 1 (Monday): Mental Model Recall & Analogy
+> *Time: 3 Mins | Bloom: Understand*
+
+**Prompt:**  
+[Present a quick thought experiment connecting real life to code. E.g., "Imagine a physical whiteboard in a classroom. If 5 students try to write on the exact same spot at the exact same second, what happens? How does an Actor prevent this in software?"]
+
+- **Student Journal Box:**  
+  ```text
+  [1-2 sentences on race conditions vs. serialized mailboxes]
+  ```
+
+---
+
+## [REQUIRED] Day 2 (Tuesday): Rapid Code Tracing
+> *Time: 4 Mins | Bloom: Apply*
+
+**Prompt:**  
+What is the exact output printed to the console when this snippet runs?
+```swift
+func compute() async -> Int {
+    var total = 10
+    Task { total += 5 }
+    return total
+}
+```
+- **Question:** Why might the returned value be `10` instead of `15`?
+- **Answer Area:** `[Explain unstructured task detachment and race condition]`
+
+---
+
+## [REQUIRED] Day 3 (Wednesday): Quick Bug Hunt (Spot the Defect)
+> *Time: 4 Mins | Bloom: Analyze*
+
+**Prompt:**  
+Find and circle the **single syntax or concurrency bug** in this component:
+```swift
+struct UserProfileView: View {
+    @State var name: String = "Taylor"
+    
+    var body: some View {
+        Button("Reset") {
+            self.resetName()
+        }
+    }
+    
+    func resetName() {
+        name = "Guest" // <- Is this mutating allowed on a struct View?
+    }
+}
+```
+- **Correction:** [Rewrite `resetName` or state modification inline].
+
+---
+
+## [REQUIRED] Day 4 (Thursday): Visual Diagram Tracing
+> *Time: 4 Mins | Bloom: Analyze*
+
+**Prompt:**  
+Given the following state transition flow:
+`User Tap Button` $\rightarrow$ `State Flag Toggled` $\rightarrow$ `???` $\rightarrow$ `UI View Repainted`
+- **Question:** What internal engine step occurs at `???`? *(Hint: View Tree Diffing)*.
+
+---
+
+## [REQUIRED] Day 5 (Friday): Creative Synthesis & Bridge Forward
+> *Time: 5 Mins | Bloom: Evaluate / Create*
+
+**Prompt:**  
+"If you had to design a 1-sentence warning label to put on mutable global variables in a multi-threaded codebase, what would it say?"
+
+---
+
+## [REQUIRED] Teacher Answer Key & Scoring Guide
+- **Monday:** Shared memory without synchronization causes overlapping writes (data races). Actors queue requests in an isolated mailbox.
+- **Tuesday:** The spawned `Task` executes asynchronously and may not finish before `return total` executes.
+- **Wednesday:** `resetName()` mutates `name` on `self` struct; in SwiftUI, mutating `@State` is valid because the property wrapper stores value externally on heap, but function should be private or state mutated directly in button action.
+- **Thursday:** The SwiftUI dependency graph computes the structural diff between Old View and New View trees.
+- **Friday:** Open rubric: Award credit for clear mention of non-determinism, crashes, or data corruption.

package/docs/refs/templates/CHANGELOG_template.md

@@ -0,0 +1,19 @@
+---
+id: "{{ID}}"
+title: "Changelog: [Project Name]"
+type: "CHANGELOG"
+created_by: "Curriculum OS Builder"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+---
+
+# CHANGELOG: [Project Name]
+_This file maintains a persistent, append-only record of all significant changes to the project._
+
+## [v{{VERSION}}] - {{DATE}}
+### 📜 Historical Log
+- [ ] **{{DATE}}**: **Initial Setup**: Project initialization and base infrastructure setup.
+- [ ] **{{DATE}}**: **Phase 1 Complete**: All analysis and research artifacts approved.
+
+## [v0.1] - YYYY-MM-DD
+- Initial project scaffold created.

package/docs/refs/templates/CHOICE_BOARD_template.md

@@ -0,0 +1,64 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "CHOICE_BOARD"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P3-T12"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+template_contract: "artifact-template-v1"
+template_required_sections:
+  - "Learning Goals & Rule of Choice"
+  - "The 9-Square Activity Matrix"
+  - "Activity Detailed Blueprints"
+  - "Universal Assessment Rubric"
+---
+<!-- INJECT_BODY -->
+
+# 9-SQUARE CHOICE BOARD: [LESSON / UNIT TITLE]
+_Unit: U[X] | Module: M[X.X] | Target Competency: [Core Competency Name]_
+
+## [REQUIRED] Learning Goals & Rule of Choice
+- **Core Concept Anchor:** [All options must demonstrate mastery of this central invariant, e.g., "State Isolation & Safe Concurrent Mutation"].
+- **Rule of Choice (Tic-Tac-Toe / Point Model):**
+  - *Option A (Tic-Tac-Toe):* Complete 3 activities in a row (Horizontal, Vertical, or Diagonal).
+  - *Option B (Point Balance):* Reach $\ge 100\text{ pts}$ (Choose $\ge 1$ Technical Lab + $\ge 1$ Explanatory/Visual + $\ge 1$ Creative Challenge).
+
+---
+
+## [REQUIRED] The 9-Square Activity Matrix
+
+| Column 1: Analytical & Code | Column 2: Visual & Architecture | Column 3: Creative & Applied |
+| :--- | :--- | :--- |
+| **Square 1: The Bug Hunter (30 pts)**<br>Diagnose and repair a project containing 3 subtle concurrency/state race conditions. | **Square 2: The Architect's Blueprint (30 pts)**<br>Draw an exhaustive Mermaid sequence diagram illustrating data and message flow across actor boundaries. | **Square 3: Analogous Storyteller (30 pts)**<br>Write an interactive terminal game or narrative analogy explaining how runtime state binding works. |
+| **Square 4: Micro-Refactoring (40 pts)**<br>Refactor an imperative legacy codebase into declarative, pure SwiftUI components with zero state leaks. | **⭐ Square 5: Core Master Challenge (50 pts)**<br>Build a real-time reactive dashboard with live sensor simulation, debounce filtering, and test coverage. | **Square 6: Audio/Video Walkthrough (40 pts)**<br>Record a 3-minute video screencast explaining the code line-by-line using professional terminology. |
+| **Square 7: Test-Driven Lab (35 pts)**<br>Write 5 comprehensive unit & performance test cases validating boundary conditions and error throwing. | **Square 8: Comparative Whitepaper (35 pts)**<br>Write a 1-page comparative technical brief contrasting Approach A vs. Approach B with performance graphs. | **Square 9: Creative Extension (45 pts)**<br>Integrate hardware sensors, haptic feedback, or external APIs to solve a real community problem. |
+
+---
+
+## [REQUIRED] Activity Detailed Blueprints (Selected Modules)
+
+### Detail: Square 1 — The Bug Hunter
+- **Input Source Code:** Provided in `Assets/Lab/BrokenProject.zip`.
+- **Deliverable:** Pull Request diff report + clean compiled build with 0 warnings.
+
+### Detail: Square 2 — The Architect's Blueprint
+- **Format:** Mermaid Markdown Diagram (`sequenceDiagram` or `graph TD`).
+- **Required Invariants:** Must label thread context (Main Thread vs. Background Task), isolation domains, and asynchronous jump points (`await`).
+
+### Detail: ⭐ Square 5 — Core Master Challenge (Mandatory Center Option)
+- **Problem Statement:** [Real-world driving question].
+- **Acceptance Criteria:**
+  1. Clean MVVM / Actor Separation.
+  2. UI state bound reactively with no manual timer polls.
+  3. All 3 edge cases documented in unit tests.
+
+---
+
+## [REQUIRED] Universal Assessment Rubric
+| Criteria | Exemplary (4) | Proficient (3) | Developing (2) | Beginning (1) |
+| :--- | :--- | :--- | :--- | :--- |
+| **Technical Accuracy** | 100% executable, idiomatic syntax, zero race conditions. | Compiles and runs; minor non-critical styling issue. | Runs with partial errors or missing edge cases. | Does not compile or contains critical syntax bugs. |
+| **Conceptual Clarity** | Explains architectural trade-offs using rigorous engineering terms. | Explains the "how" accurately with basic rationale. | Description is vague or confuses terminology. | Cannot explain how code works. |
+| **Creativity & Autonomy** | Goes beyond specifications with thoughtful UX or performance optimizations. | Fulfills all specified criteria independently. | Needs significant scaffolding hints to complete. | Incomplete submission. |

package/docs/refs/templates/CODE_template.md

@@ -0,0 +1,70 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "CODE"
+created_by: "Curriculum OS Builder"
+phase: "P3"
+deliverable: "P3-T3"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+template_contract: "artifact-template-v1"
+template_required_sections:
+  - "Technical Overview & Architecture Blueprint"
+  - "Hardware Pinout & Wiring Configuration Matrix"
+  - "Starter Code Sandbox"
+  - "Verified Reference Solution Code"
+  - "Automated Test / Verification Script"
+  - "Common Syntax & Runtime Pitfalls Matrix"
+---
+
+# CODE LAB: [LESSON TITLE]
+
+## [REQUIRED] Technical Overview & Architecture Blueprint
+> How the code in this lab is structured and why. Reference the canonical
+> identifiers (files, types, functions) from the LESSON Code Symbol Ledger —
+> use those exact names, do not invent alternatives.
+
+- **Architecture:** [Mermaid or ASCII diagram of the components/data flow]
+- **Key decisions:** [2-4 bullets on design choices students should notice]
+
+## [CONDITIONAL] Hardware Pinout & Wiring Configuration Matrix
+> INCLUDE this section ONLY for lessons whose activity contract involves
+> physical hardware wiring. For pure software / theory lessons, OMIT the
+> entire section — do not emit placeholder wiring tables.
+
+| Component | Pin / Connection | Notes |
+|---|---|---|
+| [Component] | [Pin] | [Why this wiring] |
+
+## [REQUIRED] Starter Code Sandbox
+> Skeleton the students start from, with explicit TODO comments marking every
+> point they must implement.
+
+```[language]
+// [Starter code with TODO markers]
+```
+
+## [REQUIRED] Verified Reference Solution Code
+> 100% syntactically valid, production-ready, fully commented. Must satisfy
+> the verification script below.
+
+```[language]
+// [Complete reference solution]
+```
+
+## [REQUIRED] Automated Test / Verification Script
+> How to compile / run / verify: exact commands and expected output.
+
+```bash
+# [Verify commands]
+```
+
+- **Expected result:** [What success looks like]
+
+## [REQUIRED] Common Syntax & Runtime Pitfalls Matrix
+> Extract the Common Mistakes table VERBATIM from the canonical knowledge
+> context (KX). Do not re-invent or paraphrase — one canonical list per lesson.
+
+| Pitfall | Symptom | Fix |
+|---|---|---|
+| [From KX Common Mistakes] | [What the student sees] | [Concrete correction] |

package/docs/refs/templates/CONTENT_CONTINUITY_template.md

@@ -0,0 +1,38 @@
+---
+id: "UNIT_CODE-CONTINUITY"
+title: "Content Continuity: [PROJECT_NAME]"
+type: "CONTENT_CONTINUITY"
+created_by: "Antigravity"
+phase: "P3"
+deliverable: "P3-CONT"
+version: "v2.1"
+date: "YYYY-MM-DD"
+---
+
+# CONTENT CONTINUITY: [PROJECT_NAME]
+
+## 1. Storyline & Character Development
+- **Main Character:** [Character name, e.g., Jarvis, Explorer...]
+- **Evolution:** 
+    - [Describe how the storyline develops across Units]
+
+## 2. Pedagogical Analogies & Concepts
+
+### Unit [XX]: [Topic Name]
+| Lesson | Concept | Analogy | Notes |
+|:---:|---|---|---|
+| U01_M01_L01 | [Concept] | **[Analogy]** | [Notes] |
+
+## 3. Multimedia Assets Log
+| Asset ID | Tier | Type | Content Description |
+|---|:---:|:---:|---|
+| [ID] | [1-4] | [Image/Video] | [Description] |
+
+## 4. Hardware & Materials Used
+| Component | First Seen | Role in Storyline |
+|---|---|---|
+| [Component] | [Lesson ID] | [Role in storyline] |
+
+---
+- **Global Standard:** v2.1 (Consistency Core).
+- **Last Sync:** YYYY-MM-DD.

package/docs/refs/templates/CONTENT_STYLE_GUIDE_template.md

@@ -0,0 +1,49 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "CONTENT_STYLE_GUIDE"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P2-T3"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+template_contract: "artifact-template-v1"
+template_required_sections:
+  - "Voice & Tone"
+  - "Standard Terminology (Glossary)"
+  - "Examples & Context Rules"
+  - "Lesson Content Standards"
+---
+
+# CONTENT STYLE GUIDE
+
+
+## [REQUIRED] Voice & Tone
+- **Primary Persona:** [E.g., Encouraging mentor / Professional engineer / Storyteller]
+- **Target Audience Toning:** [E.g., Simple language for kids, technical rigor for seniors]
+- **Prohibited Phrases:** [E.g., "This is easy", "Just click this"]
+
+## [REQUIRED] Standard Terminology (Glossary)
+| Concept (English) | Standard Translation | Synonyms to Avoid | Context Notes |
+|---|---|---|---|
+| Variable | [translation] | [avoid] | Use the glossary translation for clarity |
+| Loop | [translation] | [avoid] | Avoid the non-coding term in coding context |
+| Debug | [translation] | [avoid] | Use the glossary translation for professionalism |
+
+## [REQUIRED] Examples & Context Rules
+- **Preferred Sources:** [E.g., Vietnamese daily life, urban/rural student context, popular games]
+- **Prohibited Contexts:** [E.g., Violence, military, weapons, religion, politics, heavy winter/snow examples for tropical regions]
+- **Explanation Structure:** [E.g., Analogy first -> Technical application second]
+
+## [REQUIRED] Lesson Content Standards
+_Every lesson written by @content must follow this flow:_
+1. **Warm-up / Hook:** [Scenario-based, e.g., opening question, short story]
+2. **Core Concepts:** [Maximum paragraphs per concept, use of bullet points]
+3. **Guided Practice:** [Code snippets with line-by-line comments]
+4. **Independent Practice:** [Space reserved for @activity inclusion]
+5. **Wrap-up & Checkpoint:** [Summary format, formative quiz type]
+
+## [OPTIONAL] Formatting & Code
+- **Code Blocks:** [E.g., Always use \`\`\`python, detailed comments on important functions]
+- **Visuals:** [E.g., Prefer Mermaid diagrams for algorithmic flowcharts]
+- **Markdown:** [E.g., Use **bold** for new keywords, `inline code` for variable names]

package/docs/refs/templates/CURRICULUM_FRAMEWORK_template.md

@@ -0,0 +1,63 @@
+---
+id: "{{ID}}"
+title: "{{TITLE}}"
+type: "CURRICULUM_FRAMEWORK"
+created_by: "Curriculum OS Builder"
+phase: "{{PHASE}}"
+deliverable: "P2-T1"
+version: "{{VERSION}}"
+date: "{{DATE}}"
+template_contract: "artifact-template-v1"
+template_required_sections:
+  - "Course Overview"
+  - "Global Learning Objectives"
+  - "Structural Hierarchy (Unit & Module)"
+  - "Scope & Sequence (Detailed Roadmap)"
+  - "Standard Lesson Format"
+---
+
+# CURRICULUM FRAMEWORK
+
+_Based on: LEARNER_PROFILE.md v[X]_
+
+## [REQUIRED] Course Overview
+- **Official Course Name:** [Name]
+- **Short Description:** [1–2 sentences for client/marketing materials]
+- **Primary Platform/Tools:** [E.g., Arduino Uno, Scratch 3.0, Python]
+- **Total Units:** [Number]
+- **Total Lessons:** [Number]
+- **Total Duration:** [Calculated in minutes/hours]
+
+## [REQUIRED] Global Learning Objectives
+By the end of this course, students will be able to:
+1. [Bloom Verb + Specific Content + Condition]
+2. [Bloom Verb + Specific Content + Condition]
+3. [Bloom Verb + Specific Content + Condition]
+_Note: Each objective must be measurable and observable._
+
+## [REQUIRED] Structural Hierarchy (Unit & Module)
+| Unit (UXX) | Module (UXXMYY) | Lessons | Module Objective | Lesson Codes |
+|---|---|:---:|---|---|
+| U01: [Unit 1 Name] | U01_M01: [Module Name] | [Qty] | [Specific objectives for U01_M01] | U01_M01_L01 – U01_M01_L03 |
+| U02: [Unit 2 Name] | U02_M01: [Module Name] | [Qty] | [Specific objectives for U02_M01] | U02_M01_L01 – U02_M01_L04 |
+
+## [REQUIRED] Scope & Sequence (Detailed Roadmap)
+**CONTRACT — mỗi buổi học (session) PHẢI có đúng 1 dòng, đủ 10 cột, mã bài dạng UXX_MYY_LZZ:**
+| # | Lesson Code | Title | Unit | Module | Learning Objective (Students will be able to...) | Key Concepts (Học gì) | Hands-on Deliverable (Làm được gì) | Prerequisites | Bloom | Duration (mins) |
+|---|---|---|---|---|---|---|---|---|---|:---:|
+| 01 | U01_M01_L01 | [Session title] | U01 | U01_M01 | [Measurable objective with Bloom verb: e.g. "Xác định được 4 thành phần của mạch LED"] | [Concept 1, Concept 2] | [Concrete artifact: e.g. "Mạch LED nháy cơ bản chạy trên kit thật"] | None | Understand | 90 |
+| 02 | U01_M01_L02 | [Session title] | U01 | U01_M01 | [Measurable objective] | [Concepts] | [Concrete deliverable] | U01_M01_L01 | Apply | 90 |
+
+_Rules: (a) KHÔNG truncate bằng '...' — viết ĐỦ số dòng bằng tổng số buổi của khóa; (b) Prerequisites chỉ tham chiếu mã bài TRƯỚC đó (không forward-reference); (c) Objective dùng động từ Bloom đo được (xác định/giải thích/vận dụng/thiết kế/đánh giá), không dùng 'hiểu/biết' trừu tượng; (d) Hands-on Deliverable là sản phẩm CỤ THỂ học sinh mang được ra khỏi buổi học; (e) Duration cộng lại đúng Tổng Duration của Course Overview._
+
+## [REQUIRED] Standard Lesson Format
+- **Theory Duration:** [X mins]
+- **Practice Duration:** [Y mins]
+- **Homework Included:** [Yes / No]
+- **Mini-project at end of Unit/Module:** [Yes / No]
+- **Session Resumption Protocol:** [Recap protocol for non-consecutive weekly classes]
+
+## [OPTIONAL] Standards Alignment
+| Learning Objective | Standard Code (CSTA / K12 CS / local) | Alignment Level |
+|---|---|---|
+| [Objective 1] | [E.g., TH-8.2] | [Full / Partial] |