Workflow
Export to a lab
The handoff is where designs are usually lost in translation. An export package carries the sequences, the formats a vendor expects, the validation report and a manifest naming every engine that touched the design.
5
sequence formats
2
vendor sheet formats
1
manifest
CPU
engine class
01
The goal
A design that cannot leave the system it was made in is not finished. The lab that builds it uses different software, the vendor that synthesizes it wants a specific sheet format, the patent attorney needs sequence listings in a standard nobody else uses, and the collaborator reviewing it wants to open the thing in whatever they already have.
Export exists so none of that becomes a manual re-typing exercise. One package, several representations of the same design, and a record of where each came from.
02
What is in the package
GenBank and FASTA
Fully annotated GenBank records for anything with features worth keeping, and plain FASTA for anything that will be fed to a tool that only wants letters. Both generated from the same source of truth.
SBOL
The assembly as structured parts with roles and relationships intact, so the receiving system inherits the design's logic rather than reverse-engineering it from a flat sequence.
ST.26 sequence listings
Sequence listings in the WIPO ST.26 standard for patent filings, generated from the same records as everything else so the listing and the construct cannot drift apart.
IDT and Twist order sheets
Synthesis order sheets in the formats those vendors expect, with lengths, fragment boundaries and verification primers laid out as the vendor's upload path wants them.
Addgene references
Parts with public deposits carry their Addgene identifiers through to the package, so a lab can source a known part instead of synthesizing a copy of something already on a shelf.
Manifest and validation report
Every file in the package is listed with a checksum, the engine versions that produced it, and the timestamp. The validation report travels with it.
03
Worked example
- Project
- SS-0421 — Tier 2 tomato
- Constructs exported
- 3
- Guide RNAs
- 4
- Formats
- GenBank, FASTA, SBOL, ST.26
- Vendor sheets
- IDT, Twist
- Validation report
- Attached, v12
- Manifest
- Checksums plus engine versions
Three constructs and four guides — a small, ordinary package. The parts that make it useful are the unglamorous ones. The manifest means the lab can confirm the files they received are the files that were sent. The attached validation report means they can see what was checked before it reached them. The ST.26 listing means the filing does not require someone to rebuild the sequences by hand from a PDF.
Exports are versioned. Re-exporting after a design change produces a new package rather than overwriting the old one, which matters when the first package has already been sent somewhere.
04
What you get
A downloadable archive that a wet lab, a synthesis vendor, a patent agent or a collaborator can each open and use without talking to you first. Every file traces back to a construct version, and every construct version traces back to the decisions that produced it.
Export is a CPU engine and runs free. Enterprise workspaces can have packages pushed to an endpoint by webhook instead of downloaded, which is how most recurring lab handoffs end up working once the pattern settles.
Ready to run it
Try this in the Splice Platform.
CPU engines are free to run. GPU engines run on prepaid credits.
Related