Skip to content

docs(n50): a clean N50' cannot be sourced from repo data — deferred to human-led curation#106

Merged
jam-sudo merged 1 commit into
mainfrom
docs/n50-prime-feasibility
Jul 8, 2026
Merged

docs(n50): a clean N50' cannot be sourced from repo data — deferred to human-led curation#106
jam-sudo merged 1 commit into
mainfrom
docs/n50-prime-feasibility

Conversation

@jam-sudo

@jam-sudo jam-sudo commented Jul 8, 2026

Copy link
Copy Markdown
Owner

What

Scopes the clean N50' secondary-holdout re-curation (the unbiased-generalization instrument the cherry-picking caveat calls for) and records the make-or-break finding: a clean N=50 is not sourceable from existing repository data.

Feasibility funnel (clinical_pk.json)

Step Filter Count
0 Drugs 331
1 Non-null clinical Cmax 177
2 After removing 107-holdout + 76-train (name and IK14) 16
3′ After inspection → valid clean 0
OATP1B1 non-statin substrates (spec needs ≥3) 0

The 2 nominal survivors both fail: guanfacine ER = holdout HCl-salt IK14 leak (free-base is in holdout; the counterion defeated the gate), lanthanum carbonate = inorganic combo. N=50 infeasible by −50; even N=1 isn't achievable — the clinical reference is the training source (167/331 names in holdout+train), and DrugBank covers 14,154 IK14 blocks (2026Q2 was 47/50 in DrugBank).

Why deferred to human-led curation

A real N50' needs ~50 fresh novel molecules with primary-source Cmax (no back-calc), CID-verified SMILES, ≥3 non-statin OATP1B1 substrates, oral-majority. Integrity constraint: an agent must NOT generate primary-source Cmax/SMILES/DOI for a never-touch instrument — a fabricated value is undetectable by the IK14 gate (structure membership, not value provenance) and would be worse than the 2026Q2 contamination.

E4 / public-clone reframe (a yield lever, not a rescue)

The 2.743 headline is public-clone (DrugBank hidden → no enrichment leak), so E4 (DrugBank-absent) could relax to hard-corpora-only if the N50 benchmark commits to public-clone. Even so the repo pool is ~2–5, not 50.

Changes

  • docs/research/n50_prime_feasibility_2026-07-07.md (new): the assessment.
  • dead-ends.md: DE-53 status line.
  • experiment-log.md: 2026-07-07 (cont.) entry.
  • Flags a salt-canonicalization gap in build_n50_exclusion.py's IK14 gate (false-negative-only).

(Local-only spec 2026-04-22-n50-secondary-holdout-design.md updated to match; gitignored.)

Headline 2.743 untouched. Assessment/docs only — no code, data, or curation.

…— deferred to human-led curation

A 3-agent investigation (spec/requirements, IK14 tooling, candidate-pool
feasibility) scoped the clean N50' re-curation and answered the make-or-break
question first: a clean N=50 is not sourceable from the existing reference data.

Feasibility funnel (clinical_pk.json): 331 -> 177 with Cmax -> 16 after removing
the 107-holdout + 76-train (name AND InChIKey-14) -> 2 nominal clean -> 0 valid
(guanfacine ER = holdout HCl-salt IK14 leak; lanthanum carbonate = inorganic
combo). OATP1B1 non-statin substrates in the clean pool: 0 of >=3 required.
N=50 infeasible by -50; the clinical reference IS the training source (167/331
names in holdout+train) and DrugBank covers 14,154 IK14 blocks.

A real N50' needs ~50 fresh novel molecules with human-verified primary-source
Cmax (no back-calc), CID-verified SMILES, >=3 non-statin OATP1B1 substrates,
oral-majority. Integrity constraint: an agent must not fabricate primary values
for a never-touch instrument (undetectable by the IK14 gate, worse than the
2026Q2 contamination). E4 (DrugBank-absent) could relax to hard-corpora-only if
the benchmark commits to public-clone, but the repo pool is still ~2-5.

Deferred to a separately-authorized human curation cycle; tooling (#96) + spec
are ready. Adds the feasibility doc, a DE-53 status line, an experiment-log
entry, and flags a salt-canonicalization gap in the IK14 gate. Headline 2.743
untouched.
@jam-sudo
jam-sudo enabled auto-merge (squash) July 8, 2026 01:25
@jam-sudo
jam-sudo merged commit c2d5348 into main Jul 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant