Which files carry a build history?

Three kinds. SnapGene .dna files written by a session that recorded its operations; GenBank files written by QUEEN, which embed the entire construction script in the record itself; and anything you build here, which records its own lineage as it goes. When a file has no embedded history, the tool says so rather than inventing a lineage.

Can I get the method out as text?

Yes — the protocol exports as Markdown for a paper or a notebook entry, as a CSV of every step, or as a JSON record carrying both the raw and normalised steps so a reviewer can re-check the build.

Does it show which enzymes and primers were used?

Where the record states them. Enzymes appear as chips on the header, and primer sequences appear on the steps that used them — a protocol without them cannot be ordered or run.

Record · experimental

History

Recover how a construct was made. A SnapGene file or a QUEEN-authored GenBank that carries a build history is read into the lineage of operations behind it — every step, its inputs, the enzymes and the oligos — and rendered as a process-flow graph and a numbered protocol you can follow or hand to someone else. Anything you build here records its own construction the same way, so the molecule you export carries its history with it.

Open History Open the History & provenance sample

Ten real build histories in three formats — five SnapGene source graphs (nested, wide, mixed-reaction, plus two the decoder has warnings about), four QUEEN GenBanks carrying their full construction script, two of them the same build one step apart, and an OpenCloning strategy document — plus one plain GenBank with no build record at all, which is the state most files are in

What it does

01Embedded history graph parsed from a SnapGene .dna file
02Complete construction script read from a QUEEN-authored GenBank — every operation with its arguments, its process identifier and the author’s own description
03Builds made here record their own lineage: operation, inputs, size, topology, enzymes and the oligo sequences used
04Lineage rendered as a process-flow graph and as a tree of the operations that produced the construct
05Numbered construction protocol generated from that lineage, with primer sequences as step reagents
06Per-step inputs identified, so a parent molecule is traceable
07Export as Markdown methods, a CSV of every step, or a JSON record that can be re-checked without the original file

What it runs on

Construction histories are read the way the software that wrote them reads them: the QUEEN reader is checked against real QUEEN over that project’s own demo files, and the SnapGene reader against pydna. The panel runs on @ports/provenance, @ports/rdf-syntax.

Everything runs client-side. Files are parsed in the browser and projects are saved on this machine, so an unpublished sequence is never uploaded.

Questions

Which files carry a build history?: Three kinds. SnapGene .dna files written by a session that recorded its operations; GenBank files written by QUEEN, which embed the entire construction script in the record itself; and anything you build here, which records its own lineage as it goes. When a file has no embedded history, the tool says so rather than inventing a lineage.
Can I get the method out as text?: Yes — the protocol exports as Markdown for a paper or a notebook entry, as a CSV of every step, or as a JSON record carrying both the raw and normalised steps so a reviewer can re-check the build.
Does it show which enzymes and primers were used?: Where the record states them. Enzymes appear as chips on the header, and primer sequences appear on the steps that used them — a protocol without them cannot be ordered or run.

Also searched as

SnapGene history parser · QUEEN building history reader · construct provenance tracking · plasmid build history · cloning lineage tree · construction protocol from file · dna file source graph · plasmid construction history viewer · clone genealogy tool · read SnapGene history from a .dna file · read a construction history from a GenBank file · reproducible cloning record · methods section from a plasmid file