execution-plan/README.md · UPDATED 2026-10-01
LABLOOP: week-by-week execution
2026-09-29: the sequence from week 5 on is now governed by ROADMAP-v7 (hybrid, lead-first: labdocs and GridX case studies move forward; Papers 1–3, protein, trialkit and the fund offer are parked). Weeks 0–4 below are unchanged. The weekly map further down is the module catalogue that v7 reuses.
Prepared 2026-09-12 for Peter Ciancaglini from the documents already in this folder.
Start with Week 00. There are 41 weekly folders: setup Week 00, then 40 execution weeks. No calendar start date has been assumed. At 10 hours per execution week, the base plan allocates 400 hours plus setup.
This is an execution scaffold. Weekly deliverables, posts, applications, experiments, publications and commercial outcomes have not been executed. Each week contains a detailed specs.md, a prefilled commitment.md, an empty evidence register and a review worksheet. Future artifact filenames and their acceptance criteria are specified inside that week's brief.
0101
Full learning notebooks and NotebookLM exports
01
Full learning notebooks and NotebookLM exports
Every week now has a detailed companion with plain-language foundations, numbered challenge steps, resource-stash links, worked examples, exercises/answers, evidence guidance and visual-study prompts. Open the 41-week notebook index or download all NotebookLM text exports. Each weekly cockpit page also links its notebook and individual download. The original materials, commitments, evidence and progress remain in place.
0202
How to use it
02
How to use it
- Open the current week's
specs.mdand read the linked model instructions. For weeks 00–04 the folder also holdsmaterials.md: the exact things to read and the exact YouTube videos to watch that week, each placed in a specific day block and sized to fit the 600-minute cap. - Have a model prepare that week's lesson, build instructions and draft artifacts using the ready-to-copy prompt at the bottom of the brief.
- Set dates and availability in
commitment.md; Peter owns the commitment. - Execute the blocks, record actual proof in
evidence.md, and keep the five cockpit files below current. - Complete
review.mdon Sunday. Pass gates only with evidence; carry incomplete work forward explicitly.
The five cockpit starter files live here: TODAY, PROGRESS, LOG, PARKING, QUESTIONS. They can later be copied into the private cockpit repository described by v5. This preparation has not created remote repositories or accounts.
0303
Governing documents
03
Governing documents
LABLOOP Master Plan v5 governs thesis, sequence and gates. v4 contributes company archetypes, offers, culture filter, instrument details and content templates only where v5 retains them. The v3 JSON and older HTML synthesis are historical context.
Read source decisions and feasibility notes, resources, gates, career asset requirements and artifact map. The opportunity tracker is private and begins empty; the publication register contains planned items, all not started.
0404
Weekly map
04
Weekly map
The default destination is an evidence-backed profile for applied AI/scientific-data roles in biotechnology, bioprocessing and pharma, with a parallel fixed-price consulting route. Credentials, seniority, hiring and revenue are earned and verified during execution.