Extremophile candidate ranking

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: Define the partner enzyme family, organism scope and assay-compatible inclusion rules; acquire versioned UniProt records.
• Public/profile priority: Draft an explanation of ranking uncertainty without disclosing unpublished partner information.
• Career/relationship/commercial priority: Prepare a concrete scientific collaboration ask, and a brief recruiter story about designing a decision under scarce data.

Read v6 · Week 23 · Extremophile focus before Monday. It expands this week's one-row v5 brief into daily build steps 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 V · Threads: B, EL, R · Next gate: 24

Where this week sits. - ← From: weeks 21-22 (honest model), week 18 and 21 (partner digests and call). - → Feeds: week 24 (validation plan picks 5-10 of these), week 28-30 (wet-lab results), week 31 (Paper 3 Results). - ⟳ Returns in: the partner's lab bench, which is the only place Paper 3 can become a discovery.

Goals. - 🎯 This week: partner-class sequences from UniProt; predictions with intervals; ranked candidate list; collaboration note sent. - 🏁 Next milestone: Gate 24. - 🌟 Final: candidates tested in a real lab, reported in Paper 3.

The plan (from v5 Part 7, expanded; gate and output unchanged).

v5 row: 23 | Extremophile focus | Partner's organisms and enzyme classes | Filter and enrich: sequences from UniProt for the partner's enzyme class; predict thermostability; ranked candidate list with uncertainty | Candidate list shared with the partner under a simple collaboration note - Goal: a shortlist the partner can act on. - Tue (study): the partner's organisms and enzyme classes: two review papers or book chapters the partner recommends (ask in the call), plus the partner's own last two papers. - Build: Mon: UniProt REST query for the enzyme class (EC number) filtered by taxonomy (thermophiles/psychrophiles as relevant); FASTA + metadata. Done when the query is saved in the repo and reproducible. Wed: embeddings + predictions + conformal intervals; flag sequences outside the training distribution (nearest-neighbour identity to Meltome). Done when every candidate has score, interval and novelty. Fri: ranked list (top 20) with a one-line rationale each; collaboration note (one paragraph: data ownership, authorship intent, no confidential data in public repo). Done when sent. - Sun: L-Sun (no partner names without permission): "From 30,000 proteins to 20 candidates: what a shortlist with uncertainty looks like". - Only one thing: the ranked list sent.

Mentor check. "I can hand a scientist 20 candidates and explain, for each one, why it is there and how sure I am."

• Week 22: 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 23 · Extremophile focus, 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

Material: UniProt entry documentation: accession/version, organism taxonomy, sequence and evidence; read partner enzyme methods.

Produce: One concise applied note, a worked decision/example and unresolved questions.

Understanding check: The note directly supports this week's experiment, collaboration, delivery or career action.

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

Material: Audit out-of-domain rankings against sequence similarity and training coverage; inspect five candidate explanations. Last 30 minutes: partner paper.

Produce: One concise applied note, a worked decision/example and unresolved questions.

Understanding check: The note directly supports this week's experiment, collaboration, delivery or career action.

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: Draft an explanation of ranking uncertainty without disclosing unpublished partner information.

Opportunity action: Prepare a concrete scientific collaboration ask, and a brief recruiter story about designing a decision under scarce data.

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.

If partner material is confidential, keep public-data analysis separate. No invented extremophile labels or claims of discovering a superior enzyme.

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: 24. Complete the acceptance checklist below; do not promote reputation from a draft.

• Monday artifact satisfies: Produce five traceable candidate entries with uncertainty, sequence provenance and partner-relevance rationale.
• Wednesday artifact satisfies: Every candidate has evidence, confidence limits and limitations; scores are not laboratory results.
• Friday artifact satisfies: Partner can assess feasibility and choose candidates without a hidden model assumption.
• 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.

Expanded minimum derived from the source goal: Produce five traceable candidate entries with uncertainty, sequence provenance and partner-relevance rationale.

Operational first step if stalled: open candidate-source-manifest.csv, 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 23 of this LABLOOP execution plan.
Read execution-plan/specs.md, execution-plan/DECISIONS.md,
execution-plan/GATES.md and
execution-plan/weeks/week-23-extremophile-candidate-ranking/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 23 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 expands this row into a full brief, with the gate and output unchanged, inside v6 · Week 23 · Extremophile focus. The following is source planning text, not a claim of completion. Apply the explicit evidence corrections in this specification and DECISIONS.md.