Eijex editorial archive

Research Notes

What we learned while building reproducible, evidence-aware bio-design software—including investigations that failed, assumptions that changed, and work that remains incomplete.

01

Architecture and direction

2 notes
02

Design and validation

3 notes
Design & ValidationEngineering note

Why every CAI value needs an authority record

Two CAI values for the same sequence were both mathematically correct—and still misleading when shown without their references.

· 2 minRead note →
Design & ValidationPublic-redacted case study

Why a CDS-level pass does not guarantee expression

Codon choice, protein architecture, experimental context, and measured yield belong to connected—but different—evidence layers.

· 2 minRead note →
03

Evidence and governance

3 notes
Evidence InfrastructureComputational observation

A database checkpoint is not a production evidence platform

Table presence showed that future provenance could be represented; it did not prove migration replay, leakage control, access policy, or end-to-end lineage.

· 2 minRead note →
04

Models and comparative evaluation

3 notes
External ModelsIncomplete experiment

What an incomplete HalluCodon trial still taught us

The external model never produced a candidate in this trial, but the failure exposed practical reproducibility costs that benchmark tables often omit.

· 2 minRead note →
Design & ValidationPublic-redacted case study

What a private antibody pilot taught us about reproducibility

Conflicting runs showed why a partner-derived case cannot become a publication result until seed, reference, commands, hashes, and validator outputs are frozen together.

· 2 minRead note →
05

Reliability and release engineering

3 notes