Skip to content

Three-modules version: webinar harness, slides, and cohort results#2

Open
JotaBlanco wants to merge 3 commits into
mainfrom
three-modules-version
Open

Three-modules version: webinar harness, slides, and cohort results#2
JotaBlanco wants to merge 3 commits into
mainfrom
three-modules-version

Conversation

@JotaBlanco
Copy link
Copy Markdown
Collaborator

Summary

  • Restructures the repo around three audiences (slides / experiment / runnable code) and ships the full webinar deck under webinar-presentation/, including the Cosmic-baseline templates and per-level slides.
  • Replaces the previous four-module layout with the wired-through three-module ladder (module-1/module-3/), each with 10 agents, shared code//data/ symlinks, and a cohort-runs/ artifacts directory.
  • Adds the cohort grading pipeline and final results for both engineering challenges (lateral fidelity, longitudinal closed-loop), plus the populated README.md explaining how to open slides and navigate the repo.

Test plan

  • Open webinar-presentation/presentation-index.html and click through every slide in order
  • Verify module-1/, module-2/, module-3/ each contain agent-01..agent-10 with intact code/ and data/ symlinks
  • Spot-check a cohort-runs/ artifact set renders the expected canonical-grade numbers
  • Confirm README links resolve (slide index, module folders, engineering-challenges prompts)

🤖 Generated with Claude Code

JotaBlanco and others added 3 commits June 4, 2026 17:20
Move _launch/, _grade/, and .launch-config.json from repo root into
cohort-runs/ so process artifacts are visually separated from the
deliverables (module-1..4) and the source tooling (webinar-meta).

Updates active tooling to match:
- grade-cohort-reports default out-dir is now cohort-runs/_grade/<ts>
- hook-blocker deny pattern broadened from _grade/** to cohort-runs/**
- launch-configs extra_forbidden entries point at cohort-runs/
- launch-isolated-module-agents skill docs call the orchestrator with
  <repo-root>/cohort-runs as angle_root

The orchestrator code itself is unchanged — it already takes angle_root
as an arg and resolves _launch/.launch-config.json relative to it.

Historical references inside module-X/agent-Y reports and inside the
moved dirs are left as-is — those are records of what was run at the
time.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant