"> Framework — Molecular Precision
01 — The problem

One system, described in fragments

Each of these sources describes part of the system. None necessarily describes the system as a whole.

Molecular Precision develops structured approaches that connect these fragments into explicit biological designs.

02 — From description to design

A biological system is more than its components

Describing the components of a biological system is not the same as describing its design.

A structured design must capture not only what components exist, but why they exist, how they relate to one another, what functions they perform, what requirements they satisfy and what evidence supports the decisions that created them.

This changes the question from

What is this system made from?

to

Why is this system designed this way?

For Molecular Precision, that distinction is central. A useful biological design should allow us to move through a connected chain, with each stage traceable to the others.

Intent Requirements Architecture Specification Evidence

The result is not simply better documentation. It is a more rigorous way of thinking about biological engineering.

03 — Structured biological design

Making biological designs explicit

Structured biological design makes the relationships within a system explicit rather than leaving them distributed across documents and individual knowledge.

A structured representation can describe:

components relationships functions interactions design intent requirements constraints specifications evidence provenance

This creates a representation that can be interrogated, reviewed, exchanged and progressively refined as the design develops.

The objective is not to impose unnecessary structure on scientific discovery. It is to preserve the reasoning that turns scientific discovery into an engineered biological system.

04 — SBOL3

A language for biological design

The Synthetic Biology Open Language (SBOL3) provides a standardised way of representing biological designs and the relationships between their components.

Rather than treating biological information as a collection of disconnected files, SBOL3 allows a biological design to be represented as a structured model. This supports a number of important capabilities.

Reproducibility
Designs can be communicated with greater precision, reducing dependence on undocumented assumptions.
Interoperability
Structured representations can move between researchers, organisations and computational tools.
Traceability
Components and relationships can be connected to their role within the wider design.
Reuse
Biological components and designs can be represented in ways that support comparison, modification and reuse.
Automation
Machine-readable biological designs create opportunities for computational analysis, validation and increasingly automated engineering workflows.

SBOL3 therefore represents more than a file format. It demonstrates a broader principle: biological designs become more useful when their structure and relationships are made explicit.

Explore SBOL3 services →
05 — The Nanomedicine Design Stack

A structured architecture for nanomedicine

Nanomedicine presents a particularly difficult biological design problem. A nanoparticle may appear to be a physical formulation, but its design is determined by requirements operating across several different scales.

A therapeutic objective creates biological requirements. Those biological requirements influence the delivery strategy. The delivery strategy creates requirements for the nanomaterial architecture. The material architecture must ultimately be translated into something that can be manufactured, characterised and reproduced.

These relationships are frequently discussed separately. The Molecular Precision Nanomedicine Design Stack brings them together within a single structured architecture.

L5
Clinical & Therapeutic Intent
What are we trying to achieve?

The highest layer defines the purpose of the system. Before selecting a material, particle size, targeting ligand or delivery mechanism, the therapeutic problem must be clearly defined.

This layer considers questions such as:

  • What disease or clinical problem is being addressed?
  • What therapeutic effect is required?
  • Which patient population is relevant?
  • Where must that effect occur?
  • What limitations of existing approaches are being addressed?
  • What would constitute meaningful therapeutic performance?

L5 establishes the intent from which the remainder of the design should derive.

A nanomedicine should not begin with a nanoparticle. It should begin with a therapeutic requirement.

L4
Biological Interaction
What must happen biologically?

Therapeutic intent must be translated into biological requirements. At this layer, the design considers how the proposed system must interact with the biological environment in order to achieve its intended effect.

This may include:

  • cellular and tissue targets
  • biological pathways
  • receptor interactions
  • cellular uptake
  • intracellular trafficking
  • immune interactions
  • biodistribution
  • biological barriers
  • clearance
  • toxicity considerations

The purpose of L4 is to define the biological behaviour required of the system. These requirements provide the bridge between therapeutic intent and delivery design.

L3
Delivery Architecture
How does the therapeutic reach and act at its target?

Once the required biological interaction is understood, the delivery architecture can be defined. This layer considers how the therapeutic system moves from administration to the location at which its intended biological effect must occur.

Questions may include:

  • What is the route of administration?
  • Where must the therapeutic accumulate?
  • Is active or passive targeting required?
  • How should the payload be retained and released?
  • What biological barriers must be crossed?
  • What pharmacokinetic behaviour is required?
  • What temporal profile is necessary?
  • How should the delivery system respond to its environment?

L3 translates biological requirements into functional requirements for the delivery system.

L2
Nanomaterial Architecture
What physical system can produce the required behaviour?

At L2, functional requirements become material and structural design decisions. This layer describes the physical architecture of the nanomedicine.

Relevant characteristics may include:

  • material composition
  • particle size
  • size distribution
  • morphology
  • surface chemistry
  • surface charge
  • functionalisation
  • targeting ligands
  • payload
  • payload distribution
  • encapsulation
  • release characteristics
  • structural organisation
  • stability

These parameters should not exist as an arbitrary collection of formulation variables. Each significant characteristic should have a relationship to a requirement elsewhere in the design.

Particle size, for example, is not simply a number to optimise. It may influence biodistribution, cellular uptake, clearance, payload capacity, stability and manufacturability. Structured design makes those relationships visible.

L1
Manufacturing & Specification
How can the designed system be reproduced?

A design becomes useful only when it can be implemented consistently. L1 translates the nanomaterial architecture into manufacturing requirements, measurable characteristics and specifications.

This may include:

  • material specifications
  • manufacturing parameters
  • process controls
  • critical quality attributes
  • analytical methods
  • acceptance criteria
  • particle-size specifications
  • composition
  • purity
  • stability
  • reproducibility
  • batch consistency

The purpose is not merely to describe how a nanomedicine was produced. It is to ensure that the manufactured system remains connected to the design intent established at the layers above.

06 — Traceability across the stack

Every specification should have a reason

The individual layers of the Nanomedicine Design Stack are not independent. Their value comes from the relationships between them.

A material characteristic at L2 should be traceable to a delivery requirement at L3. That delivery requirement should relate to a biological requirement at L4. The biological requirement should ultimately support the therapeutic intent established at L5.

In the opposite direction, therapeutic intent should progressively become more concrete until it reaches measurable manufacturing and specification requirements at L1. The result is a continuous chain.

Clinical Intent Biological Requirements Delivery Requirements Material Architecture Manufacturing Specification

This provides a structured answer to a deceptively simple question:

Why is this nanomedicine designed this way?

Explore nanomedicine design services →
Open implementation

From framework to structured representation

The Nanomedicine Design Stack is not intended to remain a conceptual model.

Molecular Precision is developing an open implementation using SBOL3 to explore how nanomedicine architectures can be represented as structured, machine-readable biological designs.

The implementation connects elements of the design stack through explicit relationships, providing a practical environment for examining design representation, traceability and interoperability across nanomedicine development.

The repository is openly available on GitHub for inspection, use and further development.

Open repository · GitHub
sbol3-nanomedicine-design-stack
SBOL3 · Turtle · L1 Molecular Composition
View the SBOL3 Nanomedicine Design Stack on GitHub →
07 — Design and evidence

Evidence belongs inside the design process

Biological engineering does not proceed cleanly from requirements to a finished system. Design decisions generate hypotheses. Experiments test those hypotheses. Evidence changes our understanding of the system. The design changes in response.

Molecular Precision therefore treats evidence as part of the design architecture rather than something attached to the project after development. A design decision should be capable of being connected to:

This creates a relationship between design and evidence that can evolve throughout a development programme. It also creates a clearer record of why the system developed in a particular direction.

08 — A common design philosophy

Different problems, a shared principle

SBOL3 and the Nanomedicine Design Stack operate in different areas of biological engineering. One provides a standardised language for representing biological designs. The other provides an architectural framework for reasoning about complex nanomedicine systems.

Their underlying principle is the same:

Make biological design explicit.

This is the foundation of the Molecular Precision approach.

09 — Why it matters

Why structured design matters

Structured biological design creates practical benefits throughout research and development.

Reproducibility
Design intent and system architecture can be communicated more completely, reducing reliance on undocumented assumptions.
Traceability
Technical decisions can be traced back to the requirements and reasoning that produced them.
Interoperability
Structured representations make it easier to exchange information between researchers, organisations and computational systems.
Design Review
Explicit relationships allow assumptions, inconsistencies and gaps within a design to be identified more readily.
Knowledge Transfer
Critical design knowledge becomes part of the system representation rather than remaining solely with individual researchers.
Regulatory Communication
Specifications, evidence and design rationale can be organised into a more coherent technical structure.
Computational Engineering
Machine-readable and structured biological designs create a foundation for increasingly sophisticated computational analysis, validation and automation.
10 — The direction

Towards biological engineering infrastructure

The long-term opportunity extends beyond better documentation. As biological systems become more complex, engineering them will increasingly require computational infrastructure capable of understanding components, relationships, requirements, constraints and evidence.

Structured biological design provides part of that foundation. Standards such as SBOL3 demonstrate how biological systems can be represented computationally. Frameworks such as the Nanomedicine Design Stack extend structured thinking into areas where the relationships between therapeutic intent, biology, materials and manufacturing are particularly complex.

Together, these approaches point towards biological engineering environments in which designs can be interrogated, compared, validated and progressively refined while preserving the reasoning behind them.

That is the direction Molecular Precision is exploring.

Q&A

Understanding the Molecular Precision framework

How does structured biological design work in practice?

In practice a design moves through a connected chain — Intent → Requirements → Architecture → Specification → Evidence. A therapeutic or scientific intent generates requirements; requirements shape the architecture; the architecture is realised as specifications; and evidence evaluates and refines the design as it develops. Each stage remains traceable to the others, so the reasoning behind the system is preserved. Definitions of these terms are on the Concepts page.

What problem does structured biological design solve?

Complex biological designs are often distributed across publications, experimental data, laboratory records, protocols, spreadsheets, technical specifications and tacit knowledge held by individual researchers. Structured biological design connects those fragments so that the design can be interrogated, reviewed, transferred and progressively refined without losing the reasoning behind it.

How is structured biological design different from ordinary scientific documentation?

Conventional documentation often records what was done or what a system contains. Structured biological design also records relationships: why a component exists, what requirement it satisfies, what evidence supports the decision, how it interacts with other elements and how it contributes to the intended function of the system.

How is SBOL3 used in a Molecular Precision project?

SBOL3 provides part of the machine-readable representation used to make a design’s components and relationships explicit — defining components, capturing how they relate, improving interoperability between tools, and establishing traceability. It is an enabling standard used within the broader structured-design approach rather than the approach itself. See the SBOL3 definition.

How do the five layers of the Nanomedicine Design Stack connect during a design?

The layers are not independent — their value is in the relationships between them. Therapeutic intent (L5) generates biological requirements (L4); those shape the delivery architecture (L3); which constrains the nanomaterial architecture (L2); which must ultimately become a manufacturable, measurable specification (L1). Traceability runs both ways: a material characteristic should trace back to the requirement that justifies it, and intent should translate forward into measurable specifications.

Why does the Nanomedicine Design Stack begin with therapeutic intent rather than the nanoparticle?

The framework treats material design as a consequence of requirements rather than the starting point. Therapeutic intent creates biological requirements; biological requirements influence delivery requirements; delivery requirements constrain the material architecture; and the resulting physical system must ultimately be manufacturable and measurable. This is why the framework’s starting principle is that a nanomedicine should begin with a therapeutic requirement rather than a nanoparticle.

Where does evidence fit into the Molecular Precision approach?

Evidence is treated as part of the design rather than something attached only after development. A design decision should be capable of being connected to the requirement that produced it, the reasoning supporting it, the evidence evaluating it and the specification implementing it — so the design and its supporting evidence evolve together. See evidence architecture.

Does structured biological design replace experimental science?

No. Structured biological design does not replace experimentation, biological interpretation or scientific judgement. Its purpose is to make the reasoning surrounding that work more explicit and traceable. Experiments can generate evidence that supports, challenges or changes design decisions, and the structured representation should evolve accordingly.

What are the benefits of representing biological designs in a machine-readable form?

Machine-readable representations can support interoperability between computational tools, more systematic design review, reuse of biological components and designs, computational validation, comparison between designs and increasingly automated biological-engineering workflows. The longer-term aim is not simply better documentation but biological engineering infrastructure capable of understanding relationships between components, requirements, constraints, specifications and evidence.

Is there an open implementation of the Nanomedicine Design Stack?

Yes. Molecular Precision is developing an open SBOL3 implementation to explore how elements of the Nanomedicine Design Stack can be represented as structured, machine-readable biological designs. The repository is publicly available through the project’s GitHub presence.

11 — Engagement

Work with Molecular Precision

We work with research groups, biotechnology organisations and development teams applying structured approaches to complex biological systems.

Our work includes SBOL3 implementation, biological design representation, nanomedicine architecture, design review, specification development and technical translation.

Explore services → Discuss a project →