Project Ops

RS AI Learning Lab Project Overview

The source-home overview, V0 boundary, artifact map, and working agreements.

RS AI Learning Lab is the v0 source home for Renaissance Solutions AI learning modules, labs, facilitator materials, learner handouts, contributor briefs, and pilot field notes.

This is a content and education operations repo, not a coding project. Durable curriculum artifacts live in Markdown. GitHub Issues and a GitHub Project board are the contributor-facing work system for assignments, review, kanban, and collaboration outside Obsidian.

V0 Boundary

V0 builds the spine, not the full curriculum.

Build only enough structure to:

  • explain the Learning Lab internally and maintain paired public-version placeholders on the intranet
  • organize modules by track, level, lifecycle stage, dependency, and cross-generation potential
  • sketch the first pilot-ready module candidates
  • maintain a canonical Lab Library, reusable lab templates, and contributor briefs
  • coordinate work through GitHub Issues and a Project board
  • capture decisions, roadmap changes, contributor policy, and pilot field notes

Do not build an LMS, app, database, generated schemas, scoring automation, external publishing workflow, or complete curriculum yet. The existing intranet can render internal sources and public-version placeholders; its GitHub Pages deployment is the team communication channel, not an external public release.

Current Artifact Map

  • roadmap.md: v0, pilot, and next-step expansion roadmap.
  • decisions.md: project decision log.
  • contributor-policy.md: transparent contribution, credit, review, and payment policy.
  • github-setup.md: GitHub labels, Project board columns, and contributor workflow.
  • docs/introducing-rs-ai-learning-lab.md: canonical internal Learning Lab introduction.
  • docs/get-started-here.md: learner-facing guide to the available and planned ways to engage with the Learning Lab, including Lab Notebook download and feedback guidance.
  • docs/introducing-rs-ai-learning-lab-public.md: clearly marked public-version placeholder for the paired article.
  • docs/article-pairing.md: internal-first/public-second article contract.
  • docs/track-map.md: broader working map for current and future tracks, module relationships, dependencies, reusable submodules, and holes to fill.
  • docs/embed-policy.md: rules for Obsidian-style wiki links and short embeds.
  • updates/: daily update notes with brief descriptions and links.
  • learning-library/: shared glossary terms, cheatsheets, disclaimers, and short reusable reference language for modules and labs.
  • templates/: module, contributor brief, lab contributor, facilitator-notes, and gallery-entry templates.
  • labs/: canonical home for all hands-on lab packages and their supporting materials.
  • modules/: one folder per module, with each module able to grow into classroom, short, longform, essay, article, app, or other formats. Modules link to related packages in labs/; do not create module-local lab packages.
  • contributor-briefs/: durable contributor brief artifacts; live assignment happens in GitHub Issues.
  • contributor-packs/: portable, pilot-only workbenches that let an external collaborator prepare a candidate package for local ingestion review; they do not replace GitHub governance or the canonical Lab Library.

Learning Tracks

Current V0 tracks:

  • AI Readiness and Risk Assessment Support
  • AI Literacy for the Rest of Us
  • Creative AI Makerspace
  • Contributor and Mentor Development

Future tracks are tracked in docs/track-map.md so we can see relationships and MVP opportunities without treating every brainstormed track as active build scope.

Module Lifecycle

  • Seed
  • Sketch
  • Draft
  • Pilot
  • Revised
  • Ready
  • Field Notes

Learner Availability

Learner availability is distinct from production lifecycle. Use Available, Drafting, Pilot, Planned, or Deferred to describe what a learner can access now. A broader migration of existing tracks and modules to this field is follow-on work.

Validation

For now, validation is lightweight:

rg -n ">{3}" .
git diff --check

When the Markdown contracts become more structured than human review can safely manage, add a small deterministic checker before moving to app code.

Intranet Coverage

The Learning Lab intranet publishes all durable Markdown source: project overview and operations notes, tracks, module folders, shared glossary and cheatsheets, templates, contributor briefs, review notes, and dated updates. AGENTS.md, CLAUDE.md, and GitHub pull-request configuration remain repository-control material and are intentionally not published. The Astro sync fails when another durable Markdown file is not mapped to the intranet.

Source notes may use Obsidian wiki links for shared Learning Lab references.

Use [[...]] for normal references. Use ![[...]] only for short canonical blurbs that need to appear inline, such as definitions, disclaimers, safety language, and standard warnings.

See docs/embed-policy.md for the working policy.

Source: README.md