Evolution perspective¶
Engineering iterations and directed evolution are related ideas, but they require different evidence. This page makes the distinction explicit.
Our current research scope¶
We organised our work into eleven Design–Build–Test–Learn (DBTL) cycles covering chassis characterisation, sequence design, circuit assembly and in-vitro assays. The results page presents the associated endpoint measurements.
Our current work does not establish completed directed-evolution rounds. No diversified genotype library, selection or enrichment procedure, round-by-round population lineage, sequence tracking of selected variants, or head-to-head comparison showing an evolved variant outperforming its ancestor is available in our research record.
Why the distinction matters¶
An engineering iteration can improve a design through rational redesign and testing. Directed evolution additionally needs a source of heritable variation and a selection or screening process that enriches variants against a defined performance criterion. Calling the eleven DBTL cycles “eleven evolution rounds” would misstate the records.
Evidence required to report an evolution result¶
| Evidence item | Current status |
|---|---|
| Defined evolving component and target performance metric | No complete evolution target or selection criterion has been established. |
| Starting ancestor and identifiable variant population | No library composition or lineage record is available. |
| Selection or screening procedure and round history | Not yet available. |
| Matched ancestor-versus-selected-variant measurements | Not yet available. |
| Sequences or other records connecting genotype to phenotype | No sequence files or selected-variant identifiers are available. |
We distinguish our engineering progress from the additional evidence needed to establish a directed-evolution result.