Objective
Map which AI coding tasks are viable locally vs require cloud, across all hardware tiers tested during the engagement.
What This Outcome Produces
USE-CASE-MATRIX.md (first section): A clear matrix showing use case viability by hardware tier — which tasks work locally, which require cloud, and under what conditions.
How It Builds
Participants contribute viability assessments directly to findings/USE-CASE-MATRIX.md via PRs throughout Weeks 1–3. Each contribution reflects their actual testing experience with different tasks (Tetris, enhancements, CLI tools) on their hardware.
- Establish matrix structure: rows = use cases tested, columns = hardware tiers
- Participants add their findings via PR: mark each cell Local, Cloud, Partial, or N/A
- Review PRs: ensure each entry is grounded in actual testing experience
- Merge and keep matrix organized
Complete When
- Matrix populated with viability data for all tested use cases
- Each use case has at least one tier entry
- Entries are clear and specific (not generic)
- Section marked ✅ when complete
Timeline
Active: Weeks 1–3 (participants add findings as they test)
Due: July 16, 2026 (end of Week 3)
Resources
Objective
Map which AI coding tasks are viable locally vs require cloud, across all hardware tiers tested during the engagement.
What This Outcome Produces
USE-CASE-MATRIX.md (first section): A clear matrix showing use case viability by hardware tier — which tasks work locally, which require cloud, and under what conditions.
How It Builds
Participants contribute viability assessments directly to findings/USE-CASE-MATRIX.md via PRs throughout Weeks 1–3. Each contribution reflects their actual testing experience with different tasks (Tetris, enhancements, CLI tools) on their hardware.
Complete When
Timeline
Active: Weeks 1–3 (participants add findings as they test)
Due: July 16, 2026 (end of Week 3)
Resources