Repository navigation
Conversation
…oning-sequence-visualization
ayu-atp
marked this pull request as draft
August 27, 2026 07:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains
Description
This PR adds an Inspect-native sequence-review workflow and fixes cloning
simulator/scorer defects found while reviewing the saved model traces.
Simulator and verifier changes
restriction assembly while retaining wrappers for the upstream behavior pinned
at
c028ecdcf144b55ffcd92b68be45081df5628c20.Empty-vector/dropout reassembly remains a plausible candidate; products that
restore Type IIS sites rank below site-free products.
extension, track fragments by input position rather than generated name, and
deduplicate reverse-complement representations.
insert-containing product.
result[0].Nested multi-product operations fail explicitly as ambiguous because the DSL
has no product-selection operator. The same candidate must pass both global
similarity and any digest validator.
normal scoring. The offline rescoring tool also supports the documented
final-plasmid corpus policy.
1-Ato2-Abecause these changes alter cloning scores.The design rationale, audit findings, and modeling limits are documented in
src/lab_bench_2/CLONING_SIMULATOR_V2.md.Inspect review tooling
coordinate ticks, topology, digest sites/fragments, sequence differences,
FASTA views, and recursive sequence provenance.
the five-copy mCherry reference remain visible.
regenerating model answers. Original scores, explanations, task version, and
aggregate metrics are preserved in metadata.
Rescored saved submissions
The six
*_simulator_v2_reviewed.evalfiles reuse the recorded answers and includethe rendered comparison event. They have internally updated
2-Aaggregatemetrics; the original
1-Asummaries remain in metadata.cloning_11taskscloning_2tasks_2epochscloning_6tasks_rerun_6Mcloning_sorcs2_after_session_fixgpt56sol_8tasks_method_blindgpt56sol_smoke_2tasks_hintedAcross 32 stored submissions, 11 verdicts change from incorrect to correct. One
method-blind GPT-5.6-sol answer passes using Gibson candidate 3 of 14, directly
showing why the first candidate is not authoritative. The SORCS2 answer now forms
an amplicon but remains incorrect at 0.839761 sequence similarity.
Validation
make check: all 7 enforced checks pass. Advisory failures are the pre-existingprivate Inspect API import, generated-README dirty-tree heuristic, and a local
markdownlint Node SSL bootstrap issue.
Inspect tests pass when
INSPECT_TRACE_FILEis placed under/private/tmp.Checklist
Are you adding a new eval?
Does this change affect existing eval(s)?
Does this change affect how future contributors write or submit evaluations (e.g. new required fields, changed tooling, updated conventions)?