---
id: M08-L04
title: "Apply the workflow to your own project"
module: M08
chapters: "18"
checkpoint: "CP09 or learner project"
---

# M08-L04 — Apply the workflow to your own project

Complete one bounded transfer task and evaluate the entire effort. Use an appropriate local project or the supplied CP09 README clarification: distinguish malformed fixture exit 2 from valid replay that intentionally produces FAULT and can exit 0.

Write a brief with goal, source identity, context, scope, and acceptance criteria. Preserve the baseline. Choose checks that establish the requested change without adding unrelated features. If you compare manual and AI-assisted approaches, use separate identical starts and common criteria.

Measure preparation, editing/generation, review/repair, verification, and waiting. Generation time alone is not verified delivery time. Record unmeasured values as unmeasured rather than inventing plausible numbers. A single run supports a limited observation, not a permanent tool ranking.

For the README task, read formats and fixtures, make a bounded wording edit, and run the relevant replay examples. Do not alter the intentionally malformed fixture just to make all commands succeed. Preserve the distinction between input validity, policy state, and process result.

Create a maintenance table with current dependency/source, review trigger, and relevant check. A compiler update needs build/behavior evidence; a skill trigger change needs selection cases; a link repair needs navigation/render checks. Expand verification when a change or finding justifies it.

Transfer the workflow before copying board-specific facts. New variants need exact primary sources and their own physical evidence if deployed. The core course requires no new framework, subscription, board, or public release. Finish with a concise handoff linked to actual results.

## Reading the recorded demonstration

Git's LF/CRLF message in the recording describes line-ending conversion in the Windows checkout. It is not a replay failure. The demonstrated manual README task produces the expected replay exits 0 and 2. Its elapsed time includes deliberate presentation pauses; unmeasured preparation, active work and review time remain unmeasured, and this run does not establish an AI productivity comparison.

## Resources and completion

Read Chapter 18 and the matching Sensor Monitor checkpoint README, requirements, and evidence notes. Project paths are relative to its root. Figures: SS18-01, SS18-02, SS18-03. Attempt the [exercise](exercise.md), preserve actual results, then use the separate instructor answer key. 

Source resources: [Chapter 18](../../../../book/chapters/ch18/chapter.md); [checkpoint and recovery map](../../../../examples/sensor-monitor/docs/checkpoints.md). Use the README and requirements inside your named checkpoint; the repository's final CP09 files include features absent from earlier stages. The [capstone rubric](../capstone-rubric.md) defines scoring and mandatory evidence gates.