Paper 1 preprint gate

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: Incorporate received human review, finalize author/affiliation/availability details and verify the venue's current scope and submission requirements.
• Public/profile priority: Prepare Paper 1 launch package and Google Scholar setup checklist; replace 2,000 with actual dataset N in the headline.
• Career/relationship/commercial priority: Ask the GridX contact for three relevant introductions; share the paper with the existing network and evidence-oriented recruiters.

Read v6 · Week 16 · GATE 16: Paper 1 on bioRxiv (L3) 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 IV · Threads: B, M, FL, EL (literacy), R · GATE 16

Where this week sits. - ← From: weeks 5-15 (everything FermLit). - → Feeds: week 17 (conformal intervals in Paper 2), weeks 17, 21-23 (ESM-2 is the engine of Paper 3), week 19 (applications and site), week 27 (offer built on preprints), week 36 (journal submission). - ⟳ Returns in: every message you send from now on; the preprint is your business card.

Goals. - 🎯 This week: bioRxiv submitted with code and data DOIs; LinkedIn article; preprint sent to 10 founders and 3 companies; ESM-2 embedding 100 sequences; conformal intervals on the soft sensor. - 🏁 This gate (16): L3 preprinted. - 🌟 Final: the credential that turns "who is this?" into "I read your preprint".

Mentor check. "I am the author of a preprint with a DOI. I can explain conformal coverage and what a protein embedding is."

• Week 15: 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 16 · GATE 16: Paper 1 on bioRxiv (L3), 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.

Biology/domain unit

Source unit: B16 · Protein language models

Material: Lin et al. 2023, "Evolutionary-scale prediction of atomic-level protein structure with a language model" (ESM-2), read the abstract, intro and figures; MIT 6.874 protein lecture (Kellis, YouTube "Deep Learning in Life Sciences 2021")

Produce: ESM-2 650M running on the 3050, embedding 100 sequences

Understanding check: You can explain what an embedding of a protein is

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: M16 · Uncertainty you can defend

Material: Angelopoulos & Bates, "A Gentle Introduction to Conformal Prediction" — arxiv.org/abs/2107.07511, sections 1-2

Produce: Conformal intervals on the soft sensor

Understanding check: Paper 2 reports coverage

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.

Branding: Prepare Paper 1 launch package and Google Scholar setup checklist; replace 2,000 with actual dataset N in the headline.

Opportunity action: Ask the GridX contact for three relevant introductions; share the paper with the existing network and evidence-oriented recruiters.

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.

Public availability depends on moderation. Protein embeddings this week are a bounded smoke check; record actual VRAM/runtime and use a smaller documented checkpoint if needed.

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 Gate 16: Paper 1.

Required proof: Public bioRxiv preprint DOI. Submission receipt alone leaves the public gate pending.

Reputation interpretation: L3 when public. Record target, forecast, actual date and evidence link. The original gate stays incomplete until the required external proof exists.

• Monday artifact satisfies: The author-approved manuscript has no unresolved essential evidence gaps.
• Wednesday artifact satisfies: Submission is documented; L3 is recorded only after a public preprint exists.
• Friday artifact satisfies: Every draft uses the real public link or clearly says manuscript/submitted.
• 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 submission.

Operational first step if stalled: open paper-1-final-audit.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 16 of this LABLOOP execution plan.
Read execution-plan/specs.md, execution-plan/DECISIONS.md,
execution-plan/GATES.md and
execution-plan/weeks/week-16-paper-1-preprint-gate/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 16 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 16 · GATE 16: Paper 1 on bioRxiv (L3). The following is source planning text, not a claim of completion. Apply the explicit evidence corrections in this specification and DECISIONS.md.

Week 16 · GATE 16: Paper 1 on bioRxiv (L3)

• Goal: submitted.
• Tue (B16): ESM-2 paper + MIT 6.874 protein lecture; ESM-2 running.
• Thu (M16): conformal prediction sections 1-2; intervals on the soft sensor.
• Build: Mon: incorporate human review. Wed: bioRxiv submission (category: Bioengineering or Systems Biology), code and data DOIs in the paper. Fri: LinkedIn article version of the paper for non-scientists; send the preprint to the 10 founders you have talked to and the 3 scientific-data companies you admire (no ask, just the link).
• Sun: L-Sun: the preprint. X1. Gauge: L3.
• Gate 16 passes when: bioRxiv shows the DOI.
• Only one thing: the submission.