get_construction_history
Read-only
What a construct was BUILT from: the recorded operations, the molecules they consumed, how many rounds deep the build goes, and which of the 5 sources the record came from. This is the build history, not the edit history — for what CHANGED in a document and when, call get_document_history instead.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many steps to return, oldest first. All of them when omitted. | |
| query | No | Free text over the operation, the recorded command, its info field, the process id and name, and every molecule the step names — the panel’s step filter. Composes with `molecule` rather than replacing it. | |
| _files | No | The project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name. | |
| _subject | No | The record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several. | |
| document | No | File id or name. The focused document when omitted, exactly as the panel. | |
| molecule | No | Keep only the steps that produced or consumed this molecule, by its recorded name — the panel’s graph-node filter. Names that are not in the history are refused with the list of the ones that are. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| depth | Yes | longest chain of operations from a starting material to the construct — 1 is a single round, and more means it was built on builds | |
| graph | Yes | the lineage itself: `levels`, the molecule names by round with the starting materials at 0, and `edges`, every parent → product pair. This is the Graph and Lineage tabs’ own derivation, and without it a caller holding `steps` would have to rebuild it from the recorded commands | |
| steps | Yes | the recorded operations, oldest first, with their inputs, products and enzymes. A step that records a coordinate also carries `window`: the bounds as the file writes them, the molecule they are an index INTO (never this one), and the intervals of this record they project onto through the map QUEEN writes into it — empty, with a stated reason, when those bases are not in the finished molecule | |
| total | Yes | recorded operations in the whole build, before any filter | |
| inputs | Yes | molecules the history starts from: nothing recorded produced them | |
| origin | Yes | the record this was decoded out of — NOT always the document asked for: a file with no history falls back to the project, and this names what actually answered | |
| source | Yes | which of the 5 records this came from: the workbench log, a SnapGene .dna reaction graph, a QUEEN build script, an OpenCloning strategy, or an SBOL 2/3 construction record | |
| enzymes | Yes | the enzymes this build cut with, as the history records them | |
| matched | Yes | how many steps the `molecule`/`query` filters kept — the panel prints `matched/total`, and collapsing the two would make "12 of 12" and "12 of 76" the same answer | |
| cautions | Yes | only what THIS history earned — a step the decoder could not follow, products a reaction could not have made, or a limitation of the source format. Empty is the healthy case | |
| protocol | Yes | the same numbered bench-recipe protocol the panel renders and exports | |
| conclusion | Yes | one generated sentence: how much was recorded, over how many rounds, from how many starting materials, and on whose authority. The same `conclusionOf` the panel headlines | |
| derivation | Yes | the chain behind the answer: this history ← decoder ← read from ← graded against. The last link is absent for a build recorded here, which has no oracle behind it | |
| process_flow | Yes | the build as named processes: `groups` (the author’s process names, each with its operations in execution order), `operations` (the quinable call, its depth, what it consumed and produced, and its recorded arguments), and `depth`. Absent for a record that carries no re-executable command list — only a QUEEN history does — and `unavailable` with the upstream reason for the one build shape QUEEN cannot draw itself |