---
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"
  - "Phase 1: Planning & Design"
  - "Phase 2: Implementation & Discovery"
  - "Phase 3: Debugging & Testing"
  - "3-Tier Differentiation"
  - "Reflection"
---
<!-- INJECT_BODY -->

# INQUIRY-BASED ACTIVITY: [ACTIVITY TITLE]
_Unit: U[X] | Module: M[X.X] | Lesson: Lesson [XX]_

## 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?]

## 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.]

## 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."]

## Active Learning Workflow

### Phase 1: Planning & Design

> **Duration:** {{ XX }} 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

> **Duration:** {{ XX }} 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

> **Duration:** {{ XX }} 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.

## 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.]

## Reflection
- **Discussion Question:** [E.g., Why is Approach A better than B? Which part of the code runs the slowest?]