@thanh01.pmt/curriculum-kit 1.4.44 → 1.4.46

package/docs/refs/templates/HANDOVER_DOCUMENT_template.md

@@ -8,6 +8,14 @@ deliverable: "{{DELIVERABLE_CODE}}"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "Handover Information"
+  - "Deliverables Inventory"
+  - "Commitment vs. Reality Check"
+  - "Scope Exclusions"
+  - "Getting Started Guide"
+  - "Post-Handover Support Policy"
+---
 
 # CURRICULUM HANDOVER DOCUMENT
 _Handover Date: [YYYY-MM-DD] | Version: v[X.X]_

package/docs/refs/templates/KNOWLEDGE_EXPOSITION_template.md

@@ -1,3 +1,13 @@
+---
+template_required_sections:
+  - "Session Scope"
+  - "Key Terms"
+  - "Concept Narratives"
+  - "Worked Micro-Examples"
+  - "Common Mistakes"
+  - "Self-Check Questions"
+---
+
 # KNOWLEDGE_EXPOSITION: {{lesson_code}} — {{session_title}}
 
 ---
@@ -11,7 +21,7 @@ template_contract: "knowledge-exposition-v1"
 _Self-study reference for session {{lesson_code}}. Read this before the activities.
 Scope: exactly the knowledge planned for this session — no more, no less._
 
-## [REQUIRED] Session Scope
+## Session Scope
 
 - **Objective:** {{prose_objective}}
 - **New keywords:** {{new_keywords}}
@@ -19,13 +29,13 @@ Scope: exactly the knowledge planned for this session — no more, no less._
 - **Depth targets:** {{depth_targets}}
 - **You can demonstrate, after this session:** {{exit_evidence}}
 
-## [REQUIRED] Key Terms
+## Key Terms
 
 <!-- One block per term in glossary scope. Definitions MUST match GLOSSARY.json. -->
 
 {{key_terms}}
 
-## [REQUIRED] Concept Narratives
+## Concept Narratives
 
 <!-- One subsection per concept node in session scope, sized to its depth assignment:
      - ulo: WHAT + WHY (technology-independent, what it is and why it exists)
@@ -35,17 +45,17 @@ Scope: exactly the knowledge planned for this session — no more, no less._
 
 {{concept_narratives}}
 
-## [REQUIRED] Worked Micro-Examples
+## Worked Micro-Examples
 
 <!-- Minimal examples traceable to references from the domain graph. -->
 
 {{worked_examples}}
 
-## [REQUIRED] Common Mistakes
+## Common Mistakes
 
 {{common_mistakes}}
 
-## [REQUIRED] Self-Check Questions
+## Self-Check Questions
 
 <!-- 3-5 questions mapped to exit evidence. Answers at the very end. -->
 

package/docs/refs/templates/LAB_TEMPLATE.md

@@ -8,6 +8,17 @@ deliverable: "P3-T2"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "🎯 Overview"
+  - "🛠️ Environment & Setup"
+  - "📝 Lab Tasks (3-Tier Differentiation)"
+  - "🥉 Bronze (Foundational)"
+  - "🥈 Silver (Application)"
+  - "🥇 Gold (Enrichment/Creative)"
+  - "🔍 Troubleshooting & Debugging"
+  - "🏁 Submission & Check-off"
+---
+
 <!-- INJECT_BODY -->
 
 # 👨‍💻 CODE LAB: [LAB TITLE]
@@ -24,17 +35,23 @@ This lab focuses on the practical implementation of the technical concepts cover
 
 ## 📝 Lab Tasks (3-Tier Differentiation)
 
-### 🥉 Bronze (Foundational) - [X mins]
+### 🥉 Bronze (Foundational)
+
+> **Duration:** {{ XX }} mins
 **Objective:** Establish basic functionality.
 - **Task:** [e.g., Create a basic script to read data from the DHT11 sensor.]
 - **Requirement:** Code MUST be syntactically correct and run without errors.
 
-### 🥈 Silver (Application) - [Y mins]
+### 🥈 Silver (Application)
+
+> **Duration:** {{ XX }} mins
 **Objective:** Add logic and data processing.
 - **Task:** [e.g., Add a conditional statement to turn on an LED if the temperature exceeds 30°C.]
 - **Requirement:** Demonstrate understanding of control flow and data comparison.
 
-### 🥇 Gold (Enrichment/Creative) - [Z mins]
+### 🥇 Gold (Enrichment/Creative)
+
+> **Duration:** {{ XX }} mins
 **Objective:** Optimize, extend, or integrate.
 - **Task:** [e.g., Log the temperature data to a local CSV file with timestamps.]
 - **Requirement:** Show advanced resource management (file I/O, timing, or external API integration).

package/docs/refs/templates/LEARNER_PROFILE_template.md

@@ -14,29 +14,28 @@ template_required_sections:
   - "Learning Context"
   - "Client Objectives"
 ---
-
 # LEARNER PROFILE
 
 
-## [REQUIRED] Foundational Info
+## Foundational Info
 - **Age Group:** [Specific age range, e.g., 11–13 years old]
 - **Grade Level:** [E.g., Middle School / High School]
 - **Typical Class Size:** [Number of students]
 - **Learning Context:** [E.g., Public School / Coding Center / Workshop]
 
-## [REQUIRED] Entry Level
+## Entry Level
 - **Coding Experience:** [None / Basic / Intermediate / Advanced]
 - **Hardware Experience:** [None / Basic / Intermediate / Advanced]
 - **Related Prior Courses:** [List specific courses or "None"]
 
-## [REQUIRED] Learning Context
+## Learning Context
 - **Session Duration:** [Minutes]
 - **Total Sessions:** [Number]
 - **Frequency:** [E.g., 2 sessions/week]
 - **Student Equipment:** [E.g., Personal Laptop / Lab PC / Tablet]
 - **Internet Connectivity:** [Stable / Unstable / None]
 
-## [REQUIRED] Client Objectives
+## Client Objectives
 - **Core Goal:** [What the client wants students to achieve - max 3 points]
 - **Standard Alignment:** [E.g., CSTA / K12 CS Framework / Local Standards]
 

package/docs/refs/templates/LESSONS_LEARNED_template.md

@@ -8,6 +8,14 @@ deliverable: "{{DELIVERABLE_CODE}}"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "Project Metadata"
+  - "What Worked Well (Successes)"
+  - "What Didn't Work (Failures/Bottlenecks)"
+  - "Key Design Decisions (Architecture Log)"
+  - "Actionable Improvements for Future Projects"
+  - "Open Questions / Post-Deployment Monitoring"
+---
 
 # PROJECT LESSONS LEARNED
 

package/docs/refs/templates/LESSON_5E_template.md

@@ -17,13 +17,18 @@ template_required_sections:
   - "Assessment Map"
   - "Artifact Contract"
   - "B. Lesson Flow"
-  - "Artifact Linkage"
+  - "ENGAGE"
+  - "EXPLORE"
+  - "EXPLAIN"
+  - "ELABORATE"
+  - "EVALUATE"
+  - "Artifact Linkage (Master Index)"
 ---
 <!-- INJECT_BODY -->
 
 # LESSON [XX]: [LESSON TITLE] (5E Model)
 
-## [REQUIRED] A. Lesson Design Plan
+## 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
@@ -76,22 +81,30 @@ template_required_sections:
 
 ---
 
-## [REQUIRED] B. Lesson Flow
+## B. Lesson Flow
 
-### 1. ENGAGE — [X mins]
+### 1. ENGAGE
+
+> **Duration:** {{ XX }} 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]
+### 2. EXPLORE
+
+> **Duration:** {{ XX }} 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]
+### 3. EXPLAIN
+
+> **Duration:** {{ XX }} 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]
+### 4. ELABORATE
+
+> **Duration:** {{ XX }} mins
 - **Tiered Scaffolding:**
   - 🥉 **Bronze:** [Overview of the foundational task]
   - 🥈 **Silver:** [Overview of the application task]
@@ -99,7 +112,9 @@ template_required_sections:
 
 > **ACT Contract**: Detailed operational instructions must expand the Activity Sequence above and must not change the planned evidence target.
 
-### 5. EVALUATE — [X mins]
+### 5. EVALUATE
+
+> **Duration:** {{ XX }} mins
 - **Exit Ticket:** [Provide 1-2 specific questions to quickly check mastery of the success criteria.]
 - **Closing:** [Final remarks and wrap-up notes.]
 
@@ -113,7 +128,7 @@ template_required_sections:
 
 ---
 
-## [REQUIRED] Artifact Linkage (Master Index)
+## Artifact Linkage (Master Index)
 > List all satellite files used in this lesson.
 
 | Artifact File | Role in the Classroom | When to Use |

package/docs/refs/templates/LESSON_EDP_template.md

@@ -17,12 +17,16 @@ template_required_sections:
   - "Assessment Map"
   - "Artifact Contract"
   - "B. Lesson Flow"
-  - "Artifact Linkage"
+  - "ASK (Define the Problem)"
+  - "IMAGINE (Ideate)"
+  - "PLAN (Design)"
+  - "CREATE (Build & Code)"
+  - "TEST & IMPROVE (Iterate)"
+  - "SHARE & EVALUATE (Present)"
 ---
-
 # LESSON [XX]: [PROJECT TITLE] (EDP Model - Engineering Design Process)
 
-## [REQUIRED] A. Lesson Design Plan
+## 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
@@ -73,26 +77,38 @@ template_required_sections:
 
 ---
 
-## [REQUIRED] B. Lesson Flow
+## B. Lesson Flow
+
+### 1. ASK (Define the Problem)
 
-### 1. ASK (Define the Problem) — [X mins]
+> **Duration:** {{ XX }} 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]
+### 2. IMAGINE (Ideate)
+
+> **Duration:** {{ XX }} mins
 [Students brainstorm possible solutions. Teacher suggests different approaches.]
 
-### 3. PLAN (Design) — [X mins]
+### 3. PLAN (Design)
+
+> **Duration:** {{ XX }} mins
 [Students draw circuit diagrams, create flowcharts, or write pseudocode before physical assembly.]
 
-### 4. CREATE (Build & Code) — [X mins]
+### 4. CREATE (Build & Code)
+
+> **Duration:** {{ XX }} 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]
+### 5. TEST & IMPROVE (Iterate)
+
+> **Duration:** {{ XX }} mins
 [Students test their product, record bugs, and proceed with debugging/iteration.]
 
-### 6. SHARE & EVALUATE (Present) — [X mins]
+### 6. SHARE & EVALUATE (Present)
+
+> **Duration:** {{ XX }} 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.

package/docs/refs/templates/LESSON_GENERAL_template.md

@@ -17,13 +17,17 @@ template_required_sections:
   - "Assessment Map"
   - "Artifact Contract"
   - "B. Lesson Flow"
-  - "Artifact Linkage"
+  - "Warm-up / Hook"
+  - "Core Concepts"
+  - "Guided Practice"
+  - "Independent Practice"
+  - "Wrap-up & Checkpoint"
 ---
 <!-- INJECT_BODY -->
 
 # LESSON [XX]: [LESSON TITLE]
 
-## [REQUIRED] A. Lesson Design Plan
+## 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
@@ -73,14 +77,18 @@ template_required_sections:
 
 ---
 
-## [REQUIRED] B. Lesson Flow
+## B. Lesson Flow
 
-### 1. Warm-up / Hook — [X mins]
+### 1. Warm-up / Hook
+
+> **Duration:** {{ XX }} mins
 [Inquiry-based question, short game, or story to grab attention, connecting to prior knowledge or real-world applications.]
 
 ---
 
-### 2. Core Concepts — [X mins]
+### 2. Core Concepts
+
+> **Duration:** {{ XX }} mins
 
 ### Concept 1: [Concept Name]
 [Explain theory in age-appropriate language. Use real-world analogies. Max 3 paragraphs.]
@@ -92,19 +100,25 @@ template_required_sections:
 
 ---
 
-### 3. Guided Practice — [X mins]
+### 3. Guided Practice
+
+> **Duration:** {{ XX }} 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]
+### 4. Independent Practice
+
+> **Duration:** {{ XX }} 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]
+### 5. Wrap-up & Checkpoint
+
+> **Duration:** {{ XX }} 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.

package/docs/refs/templates/OUTPUT_CONSTRAINTS_template.md

@@ -8,6 +8,13 @@ deliverable: "{{DELIVERABLE_CODE}}"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "Structural Constraints"
+  - "Quantitative Constraints"
+  - "Pedagogical Constraints"
+  - "Code & Technical Constraints"
+  - "Language Constraints"
+---
 
 # CONTENT GENERATION CONSTRAINTS
 

package/docs/refs/templates/PACKAGING_SPEC_template.md

@@ -8,6 +8,14 @@ deliverable: "P3-SPEC"
 version: "v2.0"
 date: "YYYY-MM-DD"
 ---
+template_required_sections:
+  - "Package Structure & Rules"
+  - "Transformation Rules (⚡)"
+  - "A. For Students (Student Version)"
+  - "B. For Parents (Parent Version)"
+  - "C. For Managers / Clients (Client Version)"
+  - "Data Sanitization Protocol"
+---
 
 # PACKAGING & TRANSFORMATION SPECIFICATION
 

package/docs/refs/templates/PILOT_FEEDBACK_template.md

@@ -8,6 +8,12 @@ deliverable: "{{DELIVERABLE_CODE}}"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "Session Information"
+  - "Structured Feedback by Lesson Phase"
+  - "General Observations"
+  - "Overall Classification & Action (For System / Human PM)"
+---
 
 # PILOT TEACHING FEEDBACK
 _Date Recorded: [YYYY-MM-DD]_

package/docs/refs/templates/PROJECT_BRIEF_template.md

@@ -8,6 +8,14 @@ deliverable: "P1-T9"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "Project Overview"
+  - "Audience & Duration"
+  - "Learning Roadmap"
+  - "Learning Outcomes & Deliverables"
+  - "Technical Constraints"
+  - "Artifact Scope"
+---
 
 # PROJECT BRIEF: [PROJECT NAME]
 

package/docs/refs/templates/PROJECT_STATUS_template.md

@@ -8,6 +8,15 @@ deliverable: "P1-GATE"
 version: "v4.6"
 date: "YYYY-MM-DD"
 ---
+template_required_sections:
+  - "Project Summary"
+  - "Macro Pipeline (Course Lifecycle)"
+  - "High-Level Roadmap"
+  - "Detailed Progress Tracking"
+  - "Critical Links"
+  - "Changelog (Latest Only)"
+  - "🎯 Current Milestone: Phase 1 - R&D"
+---
 
 # PROJECT STATUS: [PROJECT_NAME]
 

package/docs/refs/templates/QUIZ_template.md

@@ -8,6 +8,13 @@ deliverable: "P2-T08"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "Metadata Specs"
+  - "Schema Structure"
+  - "Pedagogical Rules"
+  - "Visual Layout (Marp/Interactive)"
+---
+
 <!-- 
   Created by: Curriculum OS Builder
   Phase: P2 | Deliverable: P2-T08 (Assessment Infrastructure)

package/docs/refs/templates/QUIZ_v4.6_template.md

@@ -14,10 +14,9 @@ template_required_sections:
   - "Code Analysis / Debugging Question"
   - "Competency Rubric"
 ---
-
 # QUIZ: [LESSON TITLE]
 
-## [REQUIRED] Assessment Objectives
+## Assessment Objectives
 > One row per Learning Objective from the LESSON A1 table. Bloom level of each
 > objective MUST match the LESSON A1 Bloom verb — do not re-target.
 
@@ -25,7 +24,7 @@ template_required_sections:
 |---|---|---|---|
 | LO1 | [What this quiz verifies for LO1] | [Same Bloom verb as LESSON A1] | [Observable student output] |
 
-## [REQUIRED] Multiple-Choice Question Bank
+## Multiple-Choice Question Bank
 > ≥5 scenario-based questions, 4 options each. Every distractor must be a real,
 > common misconception from this lesson's domain (see Common Mistakes source in
 > the canonical knowledge context) — never random filler.
@@ -42,7 +41,7 @@ template_required_sections:
 
 <!-- Repeat per question. -->
 
-## [REQUIRED] Code Analysis / Debugging Question
+## Code Analysis / Debugging Question
 > One deep code-tracing task: students predict output or identify the bug.
 > Provide a complete, runnable snippet with line numbers.
 
@@ -54,7 +53,7 @@ template_required_sections:
 - **Expected answer:** [Output or bug + fix]
 - **Bloom:** [Level] — **LO:** [LO code]
 
-## [REQUIRED] Competency Rubric
+## Competency Rubric
 > 4-tier matrix tied to the Evidence column above.
 
 | Tier | Descriptor | Evidence Threshold |

package/docs/refs/templates/REFERENCE_PACK_template.md

@@ -8,6 +8,10 @@ deliverable: "{{DELIVERABLE_CODE}}"
 version: "{{VERSION}}"
 date: "{{DATE}}"
 ---
+template_required_sections:
+  - "📊 Coverage Summary"
+  - "📚 Detailed Technical References"
+---
 
 # REFERENCE PACK: Pedagogical Source Grounds
 

package/docs/refs/templates/REVIEW_GAME_template.md

@@ -10,9 +10,12 @@ date: "{{DATE}}"
 template_contract: "artifact-template-v1"
 template_required_sections:
   - "Game Rules & Setup Guide"
-  - "Round 1: Speed Round (100-200 Pts)"
-  - "Round 2: Code Duel & Debugging (300-400 Pts)"
-  - "Round 3: Final Boss Architecture Challenge (500 Pts)"
+  - "Round 1: Rapid-Fire Speed Round (100–200 Points)"
+  - "Question 1 (100 Pts):"
+  - "Question 2 (200 Pts):"
+  - "Round 2: Code Duel & Debugging (300–400 Points)"
+  - "Challenge 1 (300 Pts):"
+  - "Round 3: Final Boss Architecture Challenge (500 Points)"
   - "Kahoot / Quizizz CSV Export Format"
 ---
 <!-- INJECT_BODY -->
@@ -20,14 +23,14 @@ template_required_sections:
 # INTERACTIVE REVIEW GAME (QUIZ SHOW PACK): [UNIT / LESSON TITLE]
 _Unit: U[X] | Module: M[X.X] | Format: Live Classroom Quiz Show / Kahoot / Jeopardy Format_
 
-## [REQUIRED] Game Rules & Setup Guide
+## Game Rules & Setup Guide
 - **Format:** 3 Rounds of progressive difficulty with team buzzers or interactive clickers.
 - **Team Size:** 3-5 students per squad.
 - **Bonus Mechanic:** Teams can wager points on Round 3 (Final Boss Challenge).
 
 ---
 
-## [REQUIRED] Round 1: Rapid-Fire Speed Round (100–200 Points)
+## Round 1: Rapid-Fire Speed Round (100–200 Points)
 
 ### Question 1 (100 Pts):
 - **Category:** Vocabulary & Syntax
@@ -45,7 +48,7 @@ _Unit: U[X] | Module: M[X.X] | Format: Live Classroom Quiz Show / Kahoot / Jeopa
 
 ---
 
-## [REQUIRED] Round 2: Code Duel & Debugging (300–400 Points)
+## Round 2: Code Duel & Debugging (300–400 Points)
 
 ### Challenge 1 (300 Pts):
 - **Prompt:** First team to buzz in and explain why this code fails compilation wins 300 pts!
@@ -61,7 +64,7 @@ func updateStore(store: DataStore) async {
 
 ---
 
-## [REQUIRED] Round 3: Final Boss Architecture Challenge (500 Points)
+## Round 3: Final Boss Architecture Challenge (500 Points)
 - **Scenario:** "Design a real-time multiplayer scorekeeper using Swift 6 Actors. You have 3 minutes to draft the Actor interface on your team whiteboard."
 - **Rubric:**
   - `+200 pts:` Declared `actor ScoreKeeper`.
@@ -70,7 +73,7 @@ func updateStore(store: DataStore) async {
 
 ---
 
-## [REQUIRED] Kahoot / Quizizz CSV Export Format
+## Kahoot / Quizizz CSV Export Format
 ```csv
 Question,Option 1,Option 2,Option 3,Option 4,Correct Answer,Time Limit (sec)
 "What keyword creates an asynchronous suspension point?","defer","await","return","yield",2,20

package/docs/refs/templates/RUBRIC_template.md

@@ -12,12 +12,11 @@ template_required_sections:
   - "Assessment Overview"
   - "Assessment Rubric"
 ---
-
 # ASSESSMENT: [LESSON/PROJECT TITLE]
 
 _Unit: U[X] | Module: M[X.X] | Lesson: Lesson [XX]_
 
-## [REQUIRED] Assessment Overview
+## Assessment Overview
 - **Type:** [Select: Formative / Summative / Self-assessment / Peer-review]
 - **Format:** [Select: Short Exercise / Exit Ticket / Practical Product / Project Presentation]
 - **Learning Objectives Measured:** [Copy 1-2 LOs from the corresponding Lesson Plan]
@@ -25,7 +24,7 @@ _Unit: U[X] | Module: M[X.X] | Lesson: Lesson [XX]_
 
 ---
 
-## [REQUIRED] Assessment Rubric
+## Assessment Rubric
 _Note for @assessor: Describe SPECIFIC behaviors. Avoid vague words like "good" or "understand."_
 
 | Criteria | Weight | Excellent (4) | Proficient (3) | Developing (2) | Beginning (1) |

package/docs/refs/templates/SCIENCE_LAB_template.md

@@ -11,8 +11,14 @@ template_contract: "artifact-template-v1"
 template_required_sections:
   - "Guiding Inquiry & Driving Question"
   - "Hypothesis & Experimental Design"
+  - "Controlled Variables:"
   - "Data Collection & Code Lab Protocol"
+  - "Lab Setup & Instrumentation Code:"
+  - "Data Collection Table:"
   - "CER Scientific Conclusion (Claim, Evidence, Reasoning)"
+  - "📌 Claim (Khẳng định):"
+  - "📊 Evidence (Bằng chứng số liệu):"
+  - "🧠 Reasoning (Lập luận khoa học):"
   - "Peer Review & Verification Protocol"
 ---
 <!-- INJECT_BODY -->
@@ -20,13 +26,13 @@ template_required_sections:
 # STEM / CODE INVESTIGATION LAB (CER): [LAB TITLE]
 _Unit: U[X] | Module: M[X.X] | Domain: [Scientific / Engineering Domain]_
 
-## [REQUIRED] Guiding Inquiry & Driving Question
+## Guiding Inquiry & Driving Question
 - **Real-World Driving Question:** [E.g., "How does thread contention affect application frame rate (FPS) and memory throughput under heavy load?"]
 - **Engineering Phenomenon:** [E.g., "When two tasks write to the same mutable array simultaneously, why does the program crash intermittently rather than every single run?"]
 
 ---
 
-## [REQUIRED] Hypothesis & Experimental Design
+## Hypothesis & Experimental Design
 - **Student Hypothesis Template:**  
   > *"If we [Action / Variable Manipulation, e.g., 'isolate the shared mutable resource inside an Actor instead of using a global lock'], then [Predicted Outcome, e.g., 'data races will drop to zero and UI thread latency will remain under 16ms'] because [Scientific / Engineering Rationale]."*
 
@@ -37,7 +43,7 @@ _Unit: U[X] | Module: M[X.X] | Domain: [Scientific / Engineering Domain]_
 
 ---
 
-## [REQUIRED] Data Collection & Code Lab Protocol
+## Data Collection & Code Lab Protocol
 
 ### Lab Setup & Instrumentation Code:
 ```swift
@@ -61,7 +67,7 @@ struct BenchmarkProbe {
 
 ---
 
-## [REQUIRED] CER Scientific Conclusion (Claim, Evidence, Reasoning)
+## CER Scientific Conclusion (Claim, Evidence, Reasoning)
 > *Students must write their conclusion strictly following the 3-part CER framework:*
 
 ### 1. 📌 Claim (Khẳng định):
@@ -84,5 +90,5 @@ struct BenchmarkProbe {
 
 ---
 
-## [REQUIRED] Peer Review & Verification Protocol
+## Peer Review & Verification Protocol
 - **Reproducibility Test:** Exchange code probes with another student group to verify if their experimental results match within a $\pm 10\%$ tolerance band.