LABLOOP W14 — paper 1 full draft: full learning notebook

Paper 1 becomes a complete scientific draft. The introduction explains why the question matters; methods explain exactly what you did; results state what the measurements show; discussion explains meaning and limitations. This IMRaD structure is a chain of reasoning, not a decorative template. Statistical tests and automated judges must remain subordinate to the quality of the underlying measurement.

Your systems, software and AI connection. A manuscript resembles a technical design document with a stronger evidence obligation. Your reader must be able to trace each claim through the pipeline. Multiple-testing correction helps control misleading discoveries when asking many related questions, while effect sizes explain whether a difference matters in practice.

Dependency map from the existing programme.

• ← From: week 13 skeleton and reviewer list; weeks 5-11 artifacts.
• → Feeds: week 15 (review and human read), week 16 (submission), week 31 (Paper 3 uses the same writing process), week 36 (journal version).
• ⟳ Returns in: every future paper: your Methods style becomes your signature.

Gate and proof required by the current weekly specification.

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

The milestones are targets, not predictions of success. A prepared notebook, generated visual, course completion or draft paper is not a substitute for the required evidence. Your final profile should connect a clear scientific question to working software, trustworthy data, measured comparisons, documented limitations and your own contribution.

• Week 13: inspect its actual evidence and review; source/code artifacts must exist before the dependent task begins.

1. Open the existing commitment and previous review/evidence. Identify which required inputs are present, missing or stale. A folder name does not prove its project is complete.
2. Locate the canonical code/data repository and note its current version. The coordinating files named below live in this weekly folder; implementations and measured outputs belong in the canonical project, linked from evidence.md.
3. Read the plain-language explanation and worked example before selecting sources. Try the small calculation or reasoning exercise on paper. Mark any unfamiliar symbol or word.
4. Use the relevant refresher below inside your allocated study time. Say the idea aloud in your own words, work one example and connect it to a named output. Park material that does not unblock this week.
5. Write the next physical action in TODAY.md and start the allocated block. If a human, dataset or external event is missing, continue independent preparation and mark the dependent task pending.

You have professional experience and are rebuilding dormant foundations; unfamiliar notation is a repairable gap. For each equation, identify the question, read every symbol aloud, attach units, substitute small numbers and only then translate it to code.

From papers to trustworthy experimental records

A paper is a document; an experiment is a specific tested condition or comparison; a measurement is a value associated with that experiment. They require different identifiers. Provenance is the trail from a stored value to the document/version, paragraph, sentence or table cell that supports it. Preserve that trail even after normalization.

Missingness has several causes. “Not reported” means the source was inspected and did not provide the field under your rules. “Not extracted” means the pipeline failed or omitted it. “Inaccessible” means you could not inspect the required source. Collapsing them into a blank cell can create a false scientific conclusion about reporting quality. An LLM’s confident answer is not source evidence.

Annotation guidelines make interpretation rules explicit. Independent annotators apply the rules separately; agreement is measured before adjudication, the later process of resolving differences. A gold set is a checked reference with known limitations, not an infallible oracle. Corpus selection, annotation coverage and scoring choices all belong in Paper 1’s methods. Read a paper as question → experimental unit → method → observed result → limitation; record an abstract-only access limitation when full methods are unavailable.

What a number does—and does not—establish

An average summarizes observations but hides spread and sample support. Always ask: what was measured, on how many independent units, with what variability? An effect size is a difference or association in a meaningful scale, such as an error reduction in g/L. A small p-value does not make the effect large or useful.

A confidence interval comes from a procedure intended to cover a population quantity at a stated rate across repeated sampling under its assumptions. A credible interval describes uncertainty under a Bayesian model and its prior. A prediction interval concerns a future observation, which is different from uncertainty about an average. A bootstrap resamples data to approximate sampling variability; resample independent groups when rows are related. Report which interval you used and how, rather than writing an unlabeled “±”.

Conformal prediction uses a separate calibration procedure to construct prediction sets/intervals. Its usual guarantees depend on assumptions such as exchangeability of calibration and future cases; shifted faults or new protein families may violate them. Read the assumptions in Angelopoulos and Bates, sections 1–2 before presenting a guarantee. Identifiability asks whether the observed data can distinguish parameter values. An optimizer returning a number is not evidence that the parameter is identifiable. Plot failures and uncertainty, and keep “unknown” available as an answer.

How a professional research claim earns trust

Use a chain you can inspect: question → source data → method → output → interpretation → limitation. A claim is a sentence someone could challenge. An artifact is the file, figure, release or record that supports it. Verification explains how you checked the artifact. A screenshot can show a graph existed; code, inputs and commands allow someone to recreate it.

Every experiment needs the question or exploratory label, independent unit, data origin/rights/version/hash, baseline, split, code/config/seed, command, outputs, errors and interpretation. Keep synthetic teaching examples separate from programme results. Every public/career claim also needs your actual contribution and the correct state: prepared, sent/submitted, public, reviewed, accepted or paid/delivered.

Keep evidence in the weekly register with links to canonical project files. A DOI identifies an object; it is not peer review. A contact is not a collaborator; a submission receipt is not acceptance. These distinctions strengthen your profile because a scientist, recruiter or buyer can trust the claims that are supported. Learning evidence is personal too: explain a concept without notes, perform a small calculation, reproduce an output and identify a failure. A prepared notebook does not mean you have completed the week.

Biology B14: a null hypothesis describes a reference model for a test; a p-value measures how unusual the observed or more extreme statistic is under that model. It is not the probability the null is true. Multiple comparisons increase opportunities for misleading discoveries, so specify the correction family. AI M14: a judge model can share biases with the generator and can be sensitive to wording/order. Test it against humans by field before letting it score semantic equivalence.

Biology/domain assignment retained from the plan

Source unit: B14 · Statistics for biologists II

Material: MSMB ch. 6 (testing, multiple testing)

Produce: Multiple-testing correction applied to a FermLit comparison

Understanding check: You can defend an effect in Paper 1

AI/scientific-method assignment retained from the plan

Source unit: M14 · Evaluation and judges

Material: Stanford CS336 lecture 12 (evaluation) — cs336.stanford.edu; CS224N benchmarking lecture (judge biases)

Produce: Calibrated judge for FermLit fields

Understanding check: You can explain judge-human agreement

These inherited chapter/lecture lists are resource menus. Select the subsection that answers the named understanding check. Do not add full-course viewing to the 600-minute week. The source/stash section below supplies the existing locators and marks searches as searches.

Open this week’s resource stash or the complete weekly deck. These addresses work when the local cockpit runs on its default port; use its current address if you changed it. The public source links below also work independently of the cockpit. The weekly stash groups the existing cards; saving a card does not mark it studied.

Use core resources first, run resources when implementing a specific step, and deeper resources only after the critical work fits. Read the stated scope with one question in mind, then produce the note/calculation/artifact before opening another source. Times are inherited estimates, not extra allocations or a promise that every resource fits. Some cards contain an entire course or repository: use only the named topic/exercise.

Source status. This catalog preserves the programme’s resources. Direct links are locators, not a claim that all content was freshly inspected. Search links still need an exact source selected. The source-check log records the targeted checks and corrected FLIP locator; verify mutable versions, access rights, venues, roles and costs when executing. A NotebookLM upload does not automatically import every linked page.

A bounded way to read a scientist’s paper

Use the founder-paper slot only where scheduled. Select a paper relevant to this week through the existing resources or a verified author profile; record title, authors, year, exact URL and what full text you could access. In 30 minutes: 5 for the question and experimental unit; 10 for one relevant methods passage and figure; 10 for a digest; 5 for three questions. Your digest should say question → method → measured result with N/units → limitation → connection to this week’s artifact. If you only read the abstract, say so and leave inaccessible methods/results unknown. This notebook has not read a future partner paper on your behalf.

Use the original weekly allocation: six 90-minute days plus a 60-minute Sunday, totaling 600 minutes. Reading this notebook, creating study visuals, debugging, calls and evidence recording all consume that same capacity. This is a reference you open section by section, not an additional course to finish before building.

Monday challenge — paper-1-introduction.md

Do these steps in order.

1. Write the introduction from the verified related-work table: practical problem, current approaches, specific gap and implemented contribution.
2. For each contribution point to an existing method, resource or result.
3. Avoid “first” or “state of the art” without a supported comparison.
4. Explain in one plain-language paragraph how a scientist could use FermLit and what they should not infer from it.

Why this matters. This output closes the input/question part of the week’s evidence chain. Its acceptance criterion below determines whether the result can support the next milestone.

Output and acceptance from the specification: Write introduction and related work from verified sources, stating novelty or extension accurately. Acceptance: Each contribution corresponds to an implemented method or measured result.

Block allocation: 2 minutes open the current inputs and write the immediate action; 78 minutes carry out the steps above; 7 minutes check the acceptance criterion and record output paths/errors; 3 minutes write the next action. These sum to 90 minutes. Stop at the limit and record the exact next step rather than silently expanding the week.

Evidence to retain: the artifact or pending-state runbook, input/output paths, version/configuration, the check performed, observed result or exact failure, and your interpretation. Put the link in evidence.md. An intended filename is not proof that a measured output exists.

Wednesday challenge — paper-1-methods.md

Do these steps in order.

1. Write methods using the frozen manifests: search dates/query, eligibility, source rights, paper/experiment schema, annotation instructions, independent overlap, adjudication, model/prompt versions, splits and scoring.
2. State how absent and failed values were handled.
3. Add a data/code availability statement and exact reproduction route.
4. Ask whether a reader could reconstruct the denominator of any reported percentage.

Why this matters. This output closes the implementation/measurement part of the week’s evidence chain. Its acceptance criterion below determines whether the result can support the next milestone.

Output and acceptance from the specification: Write reproducible corpus, schema, annotation, extraction and evaluation methods with availability statement. Acceptance: A reader can identify data versions, splits, prompts, annotators and scoring rules.

Block allocation: 2 minutes open the current inputs and write the immediate action; 68 minutes carry out the steps above; 7 minutes check the acceptance criterion and record output paths/errors; 3 minutes write the next action. The remaining 10 minutes are the optional Wednesday note; reclaim them for the critical task if necessary. These sum to 90 minutes. Stop at the limit and record the exact next step rather than silently expanding the week.

Evidence to retain: the artifact or pending-state runbook, input/output paths, version/configuration, the check performed, observed result or exact failure, and your interpretation. Put the link in evidence.md. An intended filename is not proof that a measured output exists.

Friday challenge — paper-1-results.md

Do these steps in order.

1. Write results from the frozen tables and figure captions, including weak fields and negative comparisons.
2. Apply the planned correction to the declared hypothesis family, keeping exploratory tests labeled.
3. If using an LLM judge for fuzzy text, first compare it with human labels and inspect disagreements; keep strain/number/unit errors visible.
4. Write limitations before polishing the abstract so the headline remains within the evidence.

Why this matters. This output closes the verification/handoff part of the week’s evidence chain. Its acceptance criterion below determines whether the result can support the next milestone.

Output and acceptance from the specification: Write results and limitations, apply the planned multiple-testing correction and evaluate any fuzzy-field judge against humans. Acceptance: Effect sizes and denominators accompany comparisons; judge output is not ground truth.

Block allocation: 2 minutes open the current inputs and write the immediate action; 78 minutes carry out the steps above; 7 minutes check the acceptance criterion and record output paths/errors; 3 minutes write the next action. These sum to 90 minutes. Stop at the limit and record the exact next step rather than silently expanding the week.

Evidence to retain: the artifact or pending-state runbook, input/output paths, version/configuration, the check performed, observed result or exact failure, and your interpretation. Put the link in evidence.md. An intended filename is not proof that a measured output exists.

Tuesday — rebuild the domain concept through an output

1. Spend 10 minutes recalling what you know and listing the specific confusing words in the domain assignment above.
2. Spend up to 35 minutes on the relevant source subsection. Pause to define each term using the actual data or artifact, not only an analogy.
3. Spend 30 minutes producing the assigned note, drawing, calculation or bounded exercise. Label invented teaching numbers as synthetic. For applied weeks, use the exercise/decision in the current challenge.
4. Spend 10 minutes explaining what the concept changes in this week’s work. Record the explanation or write five sentences without looking.
5. Spend 5 minutes saving the output and one unresolved question. These 90 minutes include opening/closing rituals. For a source week with no new coursework, apply this rhythm to its named operational material.

Thursday — connect the model or decision to the domain

Use 5 minutes to recall the concept, 20 for the smallest relevant source section, 25 for one calculation/code application, 5 to explain it without notes and 5 to log the result. Use the remaining 30 for the scheduled founder-paper digest. If the inherited list is longer than the block, park the rest.

Write one bridge sentence: “I use [concept] in [specific artifact] because it prevents or enables [specific behavior].” Then point to the corresponding field, equation, comparison or paragraph. If you cannot locate the connection, return to the smallest worked example rather than opening more resources.

Saturday — repair the earliest dependency, then prepare study visuals

Start by reading unresolved acceptance items and choose the one that blocks the next milestone. Spend 2 minutes choosing it, 58 minutes fixing or preparing the smallest checkable result, 7 minutes checking the result and 3 minutes recording the handoff. If critical work is complete, use the remaining 20 minutes to import this notebook or prepare the next week’s sources and request one visual. If not, use those 20 minutes on the dependency. Optional sources and polish move to PARKING.md. A visual study aid does not replace the missing artifact.

Sunday — review and make next week startable

Use 20 minutes to draft a build log from one actual figure, result or failure, with correct publication state; 5 minutes to update evidence and checklist; 20 minutes to attempt the recall questions and review gaps; 15 minutes to write six next physical actions with filenames and needed inputs. Keep the original gate target and record any revised forecast separately. Actual external publishing follows the authorization available in that execution session.

Worked teaching example

Synthetic multiple-testing example: with three planned tests and family-wise alpha=0.05, Bonferroni compares each p-value to 0.05/3≈0.0167. Values 0.01, 0.03 and 0.20 leave only the first below that threshold. This correction is one option, not a substitute for meaningful effect sizes, assumptions or the predeclared analysis plan.

These are illustrative reasoning examples or explicitly synthetic numbers, not measurements obtained for your research. Recreate the calculation or reasoning before applying it to actual inputs.

Your exercise — answer before reading the solution

An automated judge says two strain names are “semantically similar.” Can that override a human-confirmed strain mismatch?

Your answer: ________

Your connection to paper-1-introduction.md: ________

Answer key

No. Similar wording does not establish biological identity. Use the field definition and source evidence; record the judge error. Report the judge as an evaluated aid rather than a new ground truth.

Five recall questions and grading guide

1. Explain this week’s purpose to a 15-year-old in three sentences. What real scientific or professional decision does it support?
2. Solve the exercise above and explain each assumption or unit, rather than copying the answer.
3. Open paper-1-introduction.md or its preparation instructions. What exact input, action, output and acceptance check make it inspectable?
4. What could make paper-1-methods.md look convincing while still being wrong? Use the week-specific risk below and name the evidence needed to detect it.
5. What does paper-1-results.md pass to the next milestone, and which claim remains unsupported until external or measured evidence exists?

Grade each answer 0 (missing/wrong), 1 (correct but vague or needs prompting), or 2 (correct, explained in your own words and tied to a concrete artifact/example). The purpose/bridge supports Q1; the separate key supports Q2; the runbook and contracts support Q3–Q5. Aim for at least 8/10 with no unresolved misconception about provenance, independence, measured versus predicted results or external status. This is a study-readiness check, not permission to pass the research gate. Save your actual score and gaps; this prepared notebook does not assign them.

What your weekly evidence record should contain

Copy the blank structure below into the existing evidence.md only when working the task. Keep earlier entries. Use actual values or PENDING with a reason; never copy illustrative numbers as results.

For documentary or commercial work, replace nonapplicable experimental fields with the actual verification (for example, source-to-claim audit or agreed scope/receipt); write “not applicable” with a reason instead of inventing a metric. For experiments, retain raw data, scripts/configs, per-case results and generated figures in the canonical project. Evidence.md is the index, not a substitute for those artifacts.

Make the skill-to-proof connection

Complete this sentence from real work: “I used [systems/software/AI capability] to answer [scientific/workflow question], implemented [artifact], checked it using [method], observed [result with context], and found [limitation]. My contribution was [specific work].” This becomes an honest portfolio/interview story. A failed experiment with a sound diagnosis is also evidence of research judgment.

The Week 40 profile should let a reader follow your claims to data/code/releases, manuscripts with exact status, independent feedback, collaboration and actual delivery. Keep a brief record now so you do not reconstruct a research history from memory later.

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

• Monday artifact satisfies: Each contribution corresponds to an implemented method or measured result.
• Wednesday artifact satisfies: A reader can identify data versions, splits, prompts, annotators and scoring rules.
• Friday artifact satisfies: Effect sizes and denominators accompany comparisons; judge output is not ground truth.
• 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.

Notebook study checklist

• I can describe the week’s question and its connection to my systems/software/AI work.
• I repaired the specific prerequisite I needed and completed the worked exercise myself.
• I used the selected stash sources and saved an applied note rather than only a viewing history.
• Each challenge has the specified output and a recorded acceptance check, or an explicit missing dependency.
• I retained source versions, units, split/decision rules, failures and limitations where applicable.
• I can distinguish illustrative, simulated, predicted and measured information in my work.
• My research/profile claims link to real evidence and use the correct external status.
• I recorded actual recall performance, next actions and any unmet gate requirement.

The specific trap to avoid this week

Do not use an LLM judge to erase strain-level mistakes or support a reporting-completeness claim without manual validation. Unsupported hypotheses stay in limitations or future work.

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.

Recovery without losing the programme’s meaning

Source-preserving minimum: Methods section.

Operational first step if stalled: open paper-1-introduction.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.

If a prerequisite concept is missing, use the first ten minutes to define it and work one tiny example. If hardware or access fails, use the allowed offline/synthetic preparation and label its scope. If a person, public identifier or payment is required, keep that event pending and finish independent work. A smaller preparation result preserves momentum; it does not replace an unmet gate.

1. Create a notebook named LABLOOP-W14 · paper 1 full draft.
2. Upload this week’s notebooklm.txt or learning-notebook.md, or paste the complete text as a source. Upload one copy, not both. Google’s source-import guidance documents text/Markdown and pasted-text sources.
3. Add the exact core source pages or permitted PDFs you selected in Section 5 as separate sources. Linked pages and local cockpit stashes are not recursively imported. Inspect what was actually imported; a video may require an available transcript. You do not need all 454 programme cards in one notebook.
4. When you execute the week, add your own notes, permitted code excerpts, results and review as separate clearly named sources. Use “Measured — …” only for actual measurements. Keep sensitive partner/client records within their permitted use.
5. Request one study output at a time using the prompts below; use the available Studio feature or ask chat for the equivalent outline. Interface/features can vary. Inspect units, labels, citations and the separation between planned and achieved work before studying or sharing a generated visual.

Week-specific visual brief

Draw an IMRaD argument from gap → method → measured result → bounded conclusion, with every claim attached to evidence.

Copy-ready prompts

Concept map / infographic

Using only the sources in LABLOOP-W14, explain “paper 1 full draft” to an adult software/systems/AI professional rebuilding science foundations after twenty years. Draw an IMRaD argument from gap → method → measured result → bounded conclusion, with every claim attached to evidence. Label each arrow with why it exists. Define every technical term at first use. Connect prerequisite → current challenge → evidence → next milestone. Mark targets, synthetic teaching numbers and measured results distinctly. Cite sources; identify missing evidence instead of inventing it.

Visual lesson / slides

Create an eight-panel visual lesson for Week 14: 1 purpose, 2 needed foundations, 3 one worked example with units, 4 Monday challenge, 5 Wednesday challenge, 6 Friday challenge, 7 common failure and verification, 8 evidence checklist and next milestone. Use simple explanations suitable for a 15-year-old without talking down to an experienced professional. Put detailed speaker notes under each panel. Use the exact artifact filenames and acceptance criteria in this notebook.

Audio or video study script

Teach Week 14 as a guided conversation: what, why, when and how. Explain the mathematical/scientific idea in words before notation. Pause for me to answer the exercise without revealing the solution; then walk through it. Connect my software experience to the scientific question. End with a rehearsal of what evidence I must retain, not a claim that I have already completed the work.

Flashcards and quiz

Make twelve cards: four term/meaning/example cards, four how/why steps from the actual challenges, two unit/assumption checks and two evidence/misconception checks. Then ask five open questions one at a time. Grade each 0–2 using the notebook rubric, explain any error, and cite the relevant section. Do not infer my competence from the existence of the notebook.

Research review rehearsal

Act as a careful research reviewer for Week 14. Ask me to defend the question, inputs, independent unit or decision basis, baseline, method, uncertainty, failure cases and scope of the claim. Use only supplied evidence. Distinguish a preparation artifact from a measured result and an external event. Finish with a claim-to-evidence table and the three smallest actions needed to close real gaps.

This notebook adds explanation and runbooks to the existing plan. The weekly specification, programme decisions and gates retain authority over sequence, scope and acceptance. The v6 master supplies the dependency map and inherited resource cards; the source catalog records their history. The teaching examples and explanatory bridge are preparation material, not executed findings.

Existing files and learning progress remain separate. Dates stay relative until you choose actual commitments. Peter owns learning, personal claims, scientific responsibility and external relationships; independent humans own their actual annotation/review contributions and partner laboratories own their laboratory execution. This notebook prepares the steps; it does not publish, contact, spend, submit or perform the programme on your behalf.