---
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"
---
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

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