Therapeutic areas & modalities · Scope of the platform

Modality-agnostic. Indication-agnostic. By construction.

The Brioche platform is built around an intent abstraction. Whatever the question — small molecule against an oncology kinase, ASO for a rare metabolic disease, peptide for an autoimmune target, biologic for a cardiovascular indication — the same engine handles it. The intent object changes; the stack does not.

01  ·  Modalities

The therapeutic modalities the engine covers.

The Discovery Engine ingests a target and a context object and returns optimized therapeutic matter against that target. Modality is a parameter of the intent, not a constraint of the engine.

M.01

Small molecules

Virtual screening, generative chemistry, predicted ADMET, synthesis prioritization. Closed-loop hit-to-lead optimization with a hand-off package ready for experimental validation.

M.02

Biologics & peptides

Sequence design against the target, predicted developability profile, immunogenicity assessment, formulation context. Hand-off ready for upstream and downstream development.

M.03

Nucleic-acid therapies

ASOs, siRNAs, mRNA constructs. Sequence design against the genomic target, predicted off-target profile, delivery and chemistry context. Precedent-aware (milasen-class IND pathway and beyond).

M.04

Antibody & protein design

Epitope analysis, candidate antibody design against structurally characterized targets, predicted developability, sequence liability profiling.

M.05

Cell & gene therapy

Construct strategy, target rationale, regulatory and manufacturing precedent — for autologous and allogeneic programs.

M.06

Combination & hybrid

Combination regimens, antibody-drug conjugates, bispecifics, modality combinations. Same intent abstraction, multiple molecular components.

Modality is a parameter of the engagement, set in the intent object at scoping. The engine does not need to be re-architected to take on a modality it has not yet served — the abstraction is built to absorb new modalities as the practice expands.
02  ·  Therapeutic areas

The therapeutic areas the engine has read.

Therapeutic area is also a parameter, not a constraint. The same engine reads the published failure record, the regulatory precedent, and the competitive set across every area below — and onboards new areas with the same source coverage and review process.

TA.01

Oncology & solid tumors

Solid tumors and hematologic malignancies. First validated proof point — solid tumor target with clinical-grade endpoints. Deep coverage of the FDA precedent set.

TA.02

Rare & orphan disease

Genetic and metabolic rare diseases with bounded patient populations and well-characterized molecular drivers. Patient-specific therapeutic context built in.

TA.03

Autoimmune & inflammatory

Autoimmune indications across rheumatology, dermatology, gastroenterology. Comparator landscape includes biologics, JAK inhibitors, and emerging modalities.

TA.04

Metabolic & endocrine

Metabolic and endocrine disease — diabetes, obesity, hepatic disease, thyroid. Long regulatory precedent record and active comparator set.

TA.05

Neurology & CNS

Neurodegenerative, psychiatric, pain, and rare neurological indications. Heavy focus on biomarker validation and trial design precedent.

TA.06

Cardiovascular & renal

Cardiovascular and renal indications — heart failure, hypertension, chronic kidney disease, comorbid conditions. Extensive regulatory precedent record.

TA.07

Infectious disease

Antimicrobial and antiviral discovery. Resistance landscape, regulatory pathway differences (LPAD, GAIN), and competitive set.

TA.08

Women's & maternal health

Reproductive, maternal-fetal, and women's health indications — historically under-served, now a growing precedent record.

TA.09

Other / scoped on request

Pediatrics, dermatology, ophthalmology, hearing & vision, GI — scoped per engagement at kickoff. The platform absorbs new areas as the practice extends.

Therapeutic area scope is set in the engagement letter. The platform's source coverage, methodology, and review process are the same in every area; what changes is the precedent set being read, which the workflow assembles dynamically.