---
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 (Selected Modules)"
  - "Detail: Square 1 — The Bug Hunter"
  - "Detail: Square 2 — The Architect's Blueprint"
  - "Detail: ⭐ Square 5 — Core Master Challenge (Mandatory Center Option)"
  - "Universal Assessment Rubric"
---
<!-- INJECT_BODY -->

# 9-SQUARE CHOICE BOARD: [LESSON / UNIT TITLE]
_Unit: U[X] | Module: M[X.X] | Target Competency: [Core Competency Name]_

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

---

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

---

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

---

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