Roadmap¶

Second Boot is structured as five phases. Each phase is gated by operational reality, not by calendar dates — moving to the next phase requires the previous phase's exit criteria to be honestly met, not just declared met.

Phase 0 — Blueprint & Foundation (current)¶

Exit criteria:

[x] Program blueprint published (this repo)
[ ] Makerspace partnership formalized in writing
[ ] First donor pipeline (one corporate IT department) committed in writing
[ ] One pilot delivery partner committed in writing (recovery center, library, school, or reentry org)
[ ] Data-wipe procedure documented and reviewed
[ ] Initial inventory tracking spreadsheet or database stood up
[ ] First local funder cultivated (Greater Kanawha Valley Foundation or equivalent)

Status: In progress. None of the partnership / donor commitments are formal yet.

Honest note: Phase 0 is documentation and relationships. It can drag on indefinitely if not actively pushed. The exit criteria above are the minimum — not the ideal — to move to Phase 1.

Phase 1 — Pilot Cohort¶

Goal: Run one cohort end-to-end with one partner, with 10–20 devices.

Activities:

First batch of donated devices through the full pipeline
Deliver curriculum to a single audience at a single partner site
Hold first graduation ceremony
Collect cohort engagement and completion data
Honest after-action review documented in this repo

Exit criteria:

10+ devices awarded
One full cohort completion documented
Cohort feedback collected from at least 50% of graduates
Wipe certificates issued and archived for every device that contained data
Partner MOU template validated against actual partner needs
After-action review published, including what didn't work

[HYPOTHESIS] A 10–20 device pilot is large enough to validate the program design and small enough to recover from operational mistakes. A larger pilot risks burning donor credibility if execution fails; a smaller pilot doesn't generate enough signal.

Phase 2 — Multi-Track Operations¶

Goal: Parallel cohorts across 2–3 partners, full curriculum delivery, quarterly ceremonies.

Activities:

Recurring cohorts at multiple partner sites
All 8 curriculum modules in active delivery (not necessarily all at every site)
First Seniors track including the committed in-home setup visit
First quarterly graduation ceremony
Donation pipeline scaled to support the cohort throughput

Exit criteria:

Year-1 targets in Impact & KPIs measured and reported honestly (whether met or not)
At least 3 active partners with documented MOUs
At least 2 ongoing corporate donor pipelines
Annual impact report published

Phase 3 — Workforce Track¶

Goal: Paid Hardware Technician Trainees and Peer Instructors as a sustained program component.

Activities:

Hardware Trainee cohort active at the makerspace, with stipend or paid status documented
Peer Instructor cohort active, teaching modules in their own community groups
Funding for the workforce component secured (likely Second Chance Act, SAMHSA, or AT&T Believes per Grants & Funding)
Outcome data collected on workforce participants — placements, retention, wage progression

Exit criteria:

10+ Hardware Trainees in active program
3+ Peer Instructors regularly teaching
At least 1 externally-validated workforce outcome (placement into external job, certification earned, etc.)
Workforce funding model documented and at least partially validated by sustained grant or sponsorship

Phase 4 — Welcome App + Inventory Software¶

Goal: The first in-repo software ships. Second Boot becomes a docs-plus-code project, not just a docs project.

Components:

Second Boot Welcome App — preinstalled on every device. Onboarding guide, community chat links, help desk contact, first-launch personalization. Likely Electron, Tauri, or web-app-launched-as-shortcut. Stack decision: Phase 3 deliverable.
Inventory database — replaces the spreadsheet from Phase 0. Tracks every device from donation through disposition. Likely small Node + SQLite or Python + SQLite service with a simple web UI. Stack decision: Phase 3 deliverable.

Exit criteria:

Welcome App shipping on every new device
Inventory database running and used as the source of truth for pipeline metrics
Both components have their own CLAUDE.md sections appended to root project CLAUDE.md
Both components ship with documentation appropriate for any future maintainer

Honest framing: Phase 4 is software work, but it should not block the program. If the docs-plus-program in Phases 0–3 are working, the software is an optimization. If they're not working, no amount of software will fix that.

Beyond Phase 4¶

Not committed; possibilities only:

Replication kit — package the program design so other organizations in other cities can adapt and run it
Connected device fleet — opt-in light telemetry on awarded devices to support post-award help-desk effectiveness (with explicit, revocable consent)
Integration with MPowerUP — bundle MPowerUP (when it has a desktop / web build) with Second Boot devices for recovery-community awardees
Integration with rlivn — refurbished tablets as rlivn client devices for caregiver-paired senior deployments

[HYPOTHESIS] Each of these is possible given the org structure but none are committed. Decide based on real Phase 3 data, not blueprint enthusiasm.

Known unknowns (program-level)¶

In addition to the cohort-outcome unknowns documented in Impact & KPIs:

Whether the makerspace partnership scales to Phase 2 throughput, or whether Second Boot needs its own dedicated workshop space
Whether the funding mix actually produces sustainable workforce wages, or whether the workforce component requires earned revenue
Whether the in-home Seniors setup visit commitment is operationally sustainable beyond pilot scale
Whether 8 curriculum modules is the right count, or whether it should consolidate

These are flagged so they can be tracked honestly through Phase 1 and Phase 2 — not papered over with confidence later.