On showing the work
A number on its own is a claim. Every result here carries the model that produced it, the assumptions it stands on, and the reason it was flagged or trusted.
Read onDesign, simulate, analyze and verify across DNA, proteins, structures and chemistry, in one environment, on one engine validated against the reference implementations of each field, open to scientists and to their AI agents alike.
One real result from the qPCR panel, shown at every depth it offers. Nothing here is a summary of the picture beside it: the picture is the product, running.
The panel writes its own conclusion from the run it just did: which thing moved, by how much, and with what interval around it. It is generated from the result, so it cannot describe a run that did not happen.
Every assumption the method rests on is stated next to the answer, and each one names its own subject rather than warning in general. An assumption nobody tested says so, and says which control would test it.
The model, the estimator, the reference it normalized to, the calibrator it compared against, and the published method it follows. Nothing is a house convention: the panel names the paper.
36 things people actually come here to do. There is no panel called “design a construct”: there are several that together do it, and each line below says which, so you can check the claim before you trust it.
All 54 live on one canvas and read the same project, so a result in one is an input to the next: design, simulate, analyze, verify.
Open the file you already have and the build comes with it: every step, every input, every parameter, readable on screen and back out again in a format that is not ours.
This is a SnapGene .dna file opened as it came, with nothing typed in. The badge names the record the decoder found; the counts are read off that record; the sentence under them is written from this decode and not from a template, so a different file says something different. Everything the two columns below promise is on this screen or one tab away from it.
jane* is a scientific computing environment for the life sciences. It covers the work a bench scientist does at a computer in a given week, annotating a plasmid, designing a primer, planning a digest, simulating a clone, fitting a curve, reading a trace, in one program rather than eleven, and it shows its working at every step.
54 surfaces are listed at §3.1 and 24 engines at §3.2. The libraries those engines derive from are registered at §4.
Runs in a browser tab. No installation, no runtime to provision, no license server to reach, and no account to create before a file can be opened.
Files are read from your disk and stay there. Nothing is uploaded, because there is no endpoint to upload to.
Free, with no tier held back.
Draw the construct, and every oligo and edit it needs.
Run the bench step before you run it at the bench.
Read what came back, at whatever depth the question needs.
Prove the thing you built is the thing you drew.
One record, moved through the four stages. Every value above was computed in this tab from data/samples/Genbank/PBR322.gb · GenBank SYNPBR322, by the same parser and the same cut-site finder the editor runs.
Each row is a live surface in the editor, not a planned one, and each sits under the stage of the arc it is reached for from.
Framework-free logic, callable without the interface, validated per §4.
No engine here is a port of a library. For each capability the published implementations are studied, the best of each is merged into one engine, and our output is then asserted byte for byte against every one of them, including the cases where they disagree with each other. Each source is cloned to disk and executed for real, so the vectors can be re-derived rather than trusted.
| Library | Language | Covers |
|---|---|---|
| pydna | Python | assembly · amplify · gel · Dseq |
| DnaCauldron | Python | Golden Gate · combinatorial assembly |
| QUEEN | Python | provenance · quine · build graph |
| DnaChisel | Python | codon optimization · constraints |
| SeqTrace | Python | Sanger trim · consensus |
| cfutils | Python | trace ↔ reference mutation calls |
| sangerseqR | R | mixed peaks · allele phasing |
| poapy | Python | partial-order MSA |
| pyMSA | Python | alignment scoring |
| crisprScore | R | guide efficiency scoring |
| cas-offinder | C++ | off-target search |
| sgffp | Python | GFF parsing |
| @gmod/bam | JS | BGZF · BAI/CSI random access |
| primer3 | C | thal ΔG · hairpin · dimer |
| seqfold | Rust | Zuker DNA folding |
| SpliceCraft | Python | RBS · mutagenesis · map image |
| ape | R | BIONJ phylogenetic trees |
| DNABarcodes | R | barcode set design |
Every one of the 18 libraries at right is cloned, run for real, and asserted against: the source language is whatever the original authors used.
The extension routes it and the contents confirm it: drop any of the 84 formats in and it just opens.
A number on its own is a claim. Every result here carries the model that produced it, the assumptions it stands on, and the reason it was flagged or trusted.
Read onWe did not port a library. We studied every serious implementation of each capability, merged the best of them into one engine, and assert our output against all of them.
Read onExcel kept turning gene names into dates, so the field renamed the genes. A spreadsheet that knows what SEPT2 is costs nothing to build.
Read onAn environment where the tools know about each other, every default is visible, and nothing is held back for a paid tier.
Drag in a GenBank record, a trace, an indexed BAM. It works out what it is and opens it.
Every engine is checked against the published implementations, byte for byte.
No sign-up, no sync, no telemetry. The file stays on the disk you opened it from.
A model with a terminal can run anything and still answers a scientific question from what it remembers. Execution is not an oracle. Point an MCP client at /mcp and the model calls the same tools these panels run, each checked against the reference implementation of its field before it ships, and each answer says how it was reached.
Beside this are three calls to the restriction-site tool an assistant gets, run just now in this page by the same code the server runs. The only EcoRI site in this circle spans the point where it closes, so reading it as a line finds nothing: the plausible answer, and the wrong one. A name that resolves to no enzyme is refused by name, because an empty list would read as no sites.
Connect an assistantNot a subset. The formats a working week actually produces, including the proprietary one.
Every result names the method and the parameters it used, and lets you change them.
A project is a folder on your disk. Move it, back it up, open it on another machine.
Every tool is in the free plan. The paid one adds a cloud behind it, never a feature you were missing.
Drop in almost any bio file. It detects the format and just opens.
Not a preview pane. Annotate, simulate, verify, and undo any of it.
Headless, framework-free, and checked against the libraries it came from.
If something here is wrong, or missing, or you want a format we do not read yet, say so at wordrobesapp@gmail.com
Talk soon.
Open it, break it, and tell us what it should have done instead. That is the whole feedback loop, and there is no form in front of it.