Glossary

Platform and execution

TermDefinition
Programmable biologyA workflow in which biological designs are expressed as computable intent, executed physically, measured, and iterated using the resulting evidence.
Autonomous labAn integrated laboratory system that can schedule and execute approved workflows across connected instruments with minimal intervention, while recording state and handling defined exceptions.
Hyderabad R&D cellProgrammable Bio's compact, fully operational autonomous laboratory setup. It is the current physical execution layer and the unit intended for scale-out.
LabOSThe software layer connecting feasibility, protocol translation, scheduling, instrument execution, quality control, and structured result delivery.
Capability registryA versioned record of which instruments, methods, materials, ranges, and constraints the current lab can support.
Experimental graphA typed record linking a design or hypothesis to executed operations, measurements, QC decisions, and outcomes.

Data and quality

TermDefinition
Execution provenanceMethod version, instrument identity, reagent lots, calibration context, timestamps, and parameters associated with a result.
Model-ready dataResults returned in a stable schema with units, metadata, QC context, and raw-file references so software can consume them without re-keying a report.
Failure labelA structured distinction between biological outcomes and process failures such as expression failure, control failure, instrument exception, or insufficient material.
DBTLDesign–Build–Test–Learn: the iterative cycle that programmable biology aims to shorten.

Status language

LabelMeaning on this site
OperationalRunning in the Hyderabad R&D setup today.
Pilot accessAvailable selectively after feasibility review and agreement.
Planning assumptionAn illustrative target used for modeling, not verified historical performance or a binding quote.
ProposedNot signed or available; subject to agreement and implementation. This applies to Apollo and future APAC collaborations.