Week 12 — endorsement and hybrid model

This week delivers the three concrete artifacts below and the supporting learning/branding/opportunity pack. The scientific or commercial outcome follows the preserved source brief, while the acceptance checks make its evidence testable. The career objective is to turn this work into something a scientist, hiring manager or buyer can inspect.

• Scientific/build priority: Prepare three endorsement/collaboration routes with verified category eligibility, paper summaries and the best available evidence link.
• Public/profile priority: Prepare a preliminary hybrid comparison with no assumed winner.
• Career/relationship/commercial priority: Open the founder, cited-author and local-academic endorsement routes; use the dataset/report while Paper 1 is still a draft.

Read v6 · Week 12 · Endorsement route opens; hybrid model v0 before Monday. It carries this week's v5 brief unchanged and adds the Welcome analogy, Learn it (▶ core and ＋ deeper sources), Run it (repos with a 20-40 minute exercise), the NotebookLM kit and the mentor check below. Standing v6 rules: resource rules, NotebookLM protocol, chapter anatomy. v6 adds depth only; it does not change a goal, gate, output or the 600-minute cap, so this specification still governs execution.

Act III · Threads: B, M, BL, R · Next gate: 13

Where this week sits. - ← From: week 1 Monod simulator (the engineer), week 8 LightGBM soft sensor (the analyst), week 4 batch-wise CV, week 8 technical report (proof of seriousness for endorsers). - → Feeds: week 17 (full learning-curve experiment), week 18 (Paper 2 draft), weeks 19-20 (endorsement closes), week 27 (pharma vocabulary in the Loop Audit offer). - ⟳ Returns in: Paper 2's central figure; the Part 9.5 routes.

Goals. - 🎯 This week: three endorsement messages sent; hybrid model v0 compared to pure GBM on 10 batches; learning-curve harness plots for 5/10/20/50 batches × 5 seeds. - 🏁 Next milestone: Gate 13 (one endorsement conversation alive). - 🌟 Final: endorsed arXiv preprint (wk 20) and the question "when does biology help the model?" answered with numbers.

Mentor check. "I can draw the hybrid architecture on a napkin, say what PAT means to a QA manager, and name my three endorsement routes."

• Week 08: inspect its actual evidence and review; source/code artifacts must exist before the dependent task begins.
• Week 10: inspect its actual evidence and review; source/code artifacts must exist before the dependent task begins.
• Week 11: inspect its actual evidence and review; source/code artifacts must exist before the dependent task begins.
• Read commitment, evidence, review and the current root TODAY/PROGRESS/QUESTIONS files.
• Read this week's chapter, v6 · Week 12 · Endorsement route opens; hybrid model v0, then the standing sections: Part 0 · how to use the document, Part 3 · the scientific thesis, Part 4 · curriculum, Part 8 · the prompt pack and Part 9 · branding and endorsement. The same sections exist in the v5 master, which remains the governing sequence; v6 reproduces them and adds depth. Retained commercial/instrument details come from v4.
• Inspect the actual canonical repository state, available data, existing figures and required human/external inputs. Never assume a previous week succeeded from its folder name.
• Verify current resource links, versions, dataset rights and any live company/venue information before relying on them. Use source catalog; explicitly record inaccessible resources.

The model must turn these into exact physical actions using the observed files and available inputs. Each 90-minute block includes start/stop rituals. All calls, posts, debugging, reading and exercises consume this same capacity.

The source lists more material than necessarily fits. Select exact excerpts for the learning objective and park the remainder; no full-course completion requirement.

Biology/domain unit

Source unit: B12 · Downstream, PAT and QbD

Material: FDA PAT guidance (2004) — fda.gov; ICH Q8(R2) sections 1-2 — ich.org

Produce: Glossary: CPP, CQA, design space, golden batch, in your words

Understanding check: You can hold a conversation with a pharma QA manager

During preparation, write one worked example connected to the week's actual task, one exercise with a separate answer key and five questions. Peter supplies answers; score explanation quality and flag misconceptions in QUESTIONS. Numeric/scientific conclusions require actual data or explicitly synthetic teaching values.

AI/scientific-method unit

Source unit: M12 · Data-driven dynamics

Material: Brunton & Kutz, Data-Driven Science and Engineering, ch. 7 (SINDy) — databookuw.com (free PDF + YouTube "Steve Brunton")

Produce: SINDy recovers Monod from simulator data

Understanding check: You can say what "system identification" is

Use the prompt pack: P1 explanation ladder, P2 concept-to-project bridge and P3 quiz. Coding practice belongs within the allocated study/build block. Where the source asks for a favorable scientific result, substitute an honest measured comparison as explained below.

Founder/scientist paper

Select one verified founder/scientific-lead paper relevant to this week's domain. Use P11; save the question, method, numerical result with context, data workflow, three author questions and one connection sentence in founder-paper.md. Keep abstract-only access limitations explicit. On source weeks with no study, prioritize the commercial/submission task and log any skipped digest.

These filenames are outputs to prepare during this week's execution; this scaffold does not claim they already exist. Drafts and measured results have different states. Technical code/data stay in the canonical project repository and are referenced from these coordinating files.

During preparation, future measured tables get column definitions, input requirements and run instructions with PENDING status. During execution, replace pending values only with measured outputs. Do not create realistic-looking fake evidence.

Branding: Prepare a preliminary hybrid comparison with no assumed winner.

Opportunity action: Open the founder, cited-author and local-academic endorsement routes; use the dataset/report while Paper 1 is still a draft.

Use career asset contracts. Publish at most the agreed cadence; one figure and one supported number or admitted failure can support multiple drafts. In long-form weeks, prepare a 1,500–2,500-word article from existing evidence within the build/buffer allocation. In release/demo weeks, prepare a 60-second script: problem, input, command/action, result, limitation and proof link.

Verify individuals, jobs and affiliations at execution time. The GridX list and v4 company map are research seeds, not current facts. Do not reveal named company weaknesses or employer/client confidential information. Keep drafted/sent/replied/booked/held statuses separate. The planning request alone does not authorize external messages or publication; honor explicit authorization in the execution session.

Fitting mechanistic parameters to a full held-out trajectory leaks future labels. SINDy needs an appropriate function library and identifiability check; recovering exact Monod kinetics is an experiment, not a guaranteed study outcome.

Apply the root scientific evidence contract: provenance; meaningful independent splits; no future-data leakage; baseline comparison; actual denominators/uncertainty; failed cases; human review where required. State whether data are simulated, public experimental, synthetic or partner-provided.

Keep source gates intact, and log scope/time conflicts in review. Missing people, money, access or results must not be replaced with invented evidence. Reduce optional polish first. A specific essential external dependency stays pending while independent preparation continues.

This is an enabling week. Its deliverables feed the next scheduled gate: 13. Complete the acceptance checklist below; do not promote reputation from a draft.

• Monday artifact satisfies: Three specific messages are ready; record actual sending and replies only if performed.
• Wednesday artifact satisfies: Mechanistic, pure ML and hybrid feature/target definitions are explicit.
• Friday artifact satisfies: A smoke run validates split isolation; full results may finish in week 17.
• Study pack is prepared; Peter's actual learning/quiz result is recorded separately.
• Branding and opportunity drafts use supported claims and the correct external-action state.
• Reproduction or document checks are recorded with file/version references.
• This week's special gate, if any, has real evidence or remains explicitly pending.
• Review, root progress/log and the next physical action are updated.

Source-preserving minimum: the three endorsement messages.

Operational first step if stalled: open endorsement-route.md, write the required inputs and produce the smallest checkable example in ten minutes. If a more urgent missing gate dependency controls the week, use the source minimum above.

If the full week does not fit, use P14: retain one gate-critical deliverable and one directly supporting study exercise; record what is skipped versus moved. Do not mark the original full gate passed merely because the minimum was completed. After a missed week, reforecast from actual evidence and avoid a second unexamined lost week.

In review, state exactly what exists, what was verified, what Peter can now explain, which external events remain pending, where the canonical code/data live, and the next file/function or draft paragraph to touch. Link each fact to evidence. Carry scientific assumptions, split definitions and rights constraints forward explicitly.

Prepare Week 12 of this LABLOOP execution plan.
Read execution-plan/specs.md, execution-plan/DECISIONS.md,
execution-plan/GATES.md and
execution-plan/weeks/week-12-endorsement-and-hybrid-model/specs.md, commitment.md, evidence.md and review.md.
Read prior prerequisite reviews and inspect actual repository/data state.
Use v5 as the governing sequence, the v6 Week 12 chapter
(LABLOOP-Master-Plan-v6.md) as the deeper walkthrough, and v4 only for
retained details.
Produce the full local preparation pack and the exact week-specific files named
in the artifact table. Give me a bounded lesson with exercises/answer key,
daily physical actions, technical runbook or draft, branding drafts and
career/commercial actions. Keep the total to 600 minutes.
Separate prepared artifacts from measured results and my learning completion.
Verify sources and do not invent metrics, citations, papers, people or outcomes.
Do not execute external communications, publication or spending unless the
current session already authorizes the specific action.
Finish by updating evidence/review and TODAY with the next physical action.

v6 reproduces this brief unchanged inside v6 · Week 12 · Endorsement route opens; hybrid model v0. The following is source planning text, not a claim of completion. Apply the explicit evidence corrections in this specification and DECISIONS.md.

Week 12 · Endorsement route opens; hybrid model v0

• Goal: three routes to an arXiv endorser started; first hybrid model.
• Tue (B12): FDA PAT + ICH Q8; glossary.
• Thu (M12): Brunton ch. 7; SINDy recovers Monod from simulator data.
• Build: [ ] Mon: Part 9.5 routes: (1) message the two most-engaged founders from week 8 with the FermLit completeness figure and ask whether they would co-author or endorse; (2) email two authors you cite heavily (Prompt P13); (3) list three local academics (UBA, UNSAM, Leloir) who publish on arXiv q-bio. Done when three messages are sent. [ ] Wed: batchlens/hybrid/: Monod ODE with parameters fitted per batch + GBM on the residual; compare to pure GBM on 10 batches. [ ] Fri: learning-curve harness: train on 5, 10, 20, 50 batches, test on held-out normal and faulty batches, 5 seeds. Done when the curve plots.
• Sun: L-Sun: "Does knowing the biology help the model? Hybrid vs pure ML at 5, 10, 20, 50 batches (first look)". L-Wed.
• Only one thing: the three endorsement messages.