Week 4: Responsible Use and Final Pipeline
Day 27: Building a Small Prototype Pipeline
Goal
Design a realistic starter project.
Learn
- A small prototype might use 20 to 100 carefully reviewed clips, consistent capture rules, extracted keypoints, gloss labels, NPZ storage, manual QA, and a simple baseline model.
- The prototype should have a narrow goal. Examples: recognize five isolated signs in controlled lighting, compare pose extraction quality, or test gloss-to-pose review workflow.
- A prototype is not production. Its job is to teach the team what breaks and what must improve.
Example
- Prototype plan: 10 signs, 3 signers, 5 clips per sign, 150 clips total, controlled camera, consent forms, DWPose extraction, NPZ files, metadata CSV, 70/15/15 split, visual QA, baseline classifier, Deaf/fluent review notes.
- Public claim: small controlled prototype for learning pipeline quality, not general ASL translation.
Practice
- Plan a tiny dataset: signs, signers, camera setup, file naming, QA rules, split rules, and evaluation method.
- Write one sentence explaining what the prototype will not claim.
Checkpoint
Before moving on
You can scope a prototype without pretending it is production-ready.
Pipeline note
Pipeline note
Small, reviewed, and repeatable beats large, messy, and untraceable.