Roadmap

V0 Purpose

RS AI Learning Lab v0 creates the project spine for training, community outreach, contributor and facilitator development, and optional connections to separate RS support when a learner or organization needs more than a module. The Lab supports the broader AI Readiness and Risk Assessment offer without becoming a required consulting or consultant-development pipeline.

The goal is not a full curriculum yet. The goal is enough structure that Martha can shape learning design, Alex can begin copy work, Tim can begin activity development, a future web designer can understand the product direction, and contributors can participate through GitHub.

Phase 1: Project Setup

Status: in progress

• Create the repo structure.
• Add local project guidance.
• Add lifecycle, track, level, dependency, and cross-generation metadata conventions.
• Add reusable module and contributor brief templates.
• Add GitHub issue templates and Project board guidance.
• Add the internal intranet introduction, its public-version placeholder, and the article-pairing contract.

Phase 2: V0 Module Sketching

Status: next

• Maintain docs/track-map.md as the working map for current tracks, expansion tracks, module relationships, dependencies, reusable submodules, and holes to fill.
• Flesh out the first 8 v0 modules enough for review.
• Identify a lab activity for each.
• Identify a take-home artifact for each.
• Mark dependencies.
• Mark cross-generation potential.
• Capture useful concepts generously during outlining; do not prune sketches to final session length yet.
• Mark material that may belong in a deeper, advanced, or tool-specific follow-up as Successor Module Candidate so later pruning can allocate it deliberately.
• Keep later modules as Seed or Sketch so they are visible but not active scope.
• Keep new expansion tracks in map/backlog scope until a specific track has enough module overlap, lab candidates, audience clarity, and review capacity to move toward MVP.

Phase 3: Activity Development

Status: next

Maintain the canonical labs/ library and use GitHub Issues to delegate package enrichment. The initial structural migration preserves current activity material while recording missing worked examples, gallery entries, facilitator guides, and reviews as scoped backlog work.

Prioritize detailed development for:

• messy prompt refinement lab
• Before You Paste sorting lab
• scam pressure-tactics lab
• optional creative image or poster lab

Phase 4: Internal Review

Status: next

Review v0 materials for:

• tone
• privacy and safety
• accessibility
• beginner clarity
• RS philosophy alignment
• contributor policy clarity

Phase 5: Pilot Prep

Status: next

• Choose one beginner module and one makerspace module for internal pilot.
• Create facilitator notes.
• Create learner handouts.
• Create a feedback form.
• Capture field notes after the pilot.

V0 Definition Of Done

V0 is complete when:

• the project exists as a standalone private repo
• the paired internal introduction and clearly marked public-version placeholder exist on the intranet
• the module template exists
• the contributor brief template exists
• the initial module backlog exists
• the first 24 module folders exist
• the first 8 build-priority modules are sketched in meaningful detail
• at least 2 hands-on labs are drafted
• the ethical contribution and payment principle is documented
• cross-generation potential is captured where appropriate
• GitHub Issues and a Project board can support contributor work

---

Source: roadmap.md