Opportunity Profile

candidate

Priority Signals

impact medium feasibility high readiness high evidence medium

Linked Tensions

No linked tensions declared.

Reusable Products

CF Formulation Scores

Target Outputs

First downstream reuse analysis for CF formulation scores.
{'Reuse decision': 'promote, revise, or deprecate the score product.'}
Candidate strains or carbon contexts for follow-up validation.

CF Formulation Score Reuse Test

Why It Matters

The Atlas already tracks CF formulation scores, but inventory marks the product as needing downstream reuse. A first consumer would show whether the score is a reusable asset or only a project-local artifact.

Review Brief

What changed: the paired derived-product page now asks whether formulation scores are generalizable enough to reuse.

Why review matters: this opportunity is the decision point for promoting, narrowing, or retiring the candidate product.

Evidence to inspect:

  • CF Formulation Scores for score components and artifacts.
  • cf_formulation_design for strict-safety filters.
  • pseudomonas_carbon_ecology and webofmicrobes_explorer for candidate consumer contexts.

Questions for reviewers:

  • What is the smallest downstream design question that would prove reuse value?
  • Which score components are cohort-specific versus generalizable?
  • What baseline should the formulation score beat?
  • Should the score remain candidate until experimental validation exists?

Evidence Base

The product connects formulation design, Pseudomonas carbon ecology, Web of Microbes context, phenotype data, and metabolism collections. That makes it a practical test case for derived-product promotion.

Work Package

Choose one reuse question: strain ranking, carbon-source prioritization, or community design constraints. Apply the existing formulation score to that question and record whether the score changes a decision relative to simpler baselines.

Decision Use

If the score improves a downstream decision, CF Formulation Scores can move toward promoted reuse. If not, the Atlas should record the failed reuse path and revise the product caveats.