Skip to content

What One Workflow Family Supports Today

This page explains what a workflow family has to contain before the repository can give it a serious public sentence.

The question is no longer whether one family has a convenient demo. The real question is whether one family now has enough benchmark, runtime, grounding, recommendation, and consequence depth that outsiders can challenge it end to end without relying on maintainer memory.

The Minimum Family Packet

For this repository, one workflow family only earns a serious sentence when it has all of the following:

  • one flagship public benchmark package
  • one companion pressure package that tests adjacent transfer or stress
  • one explicit runtime lane with rerun or replay proof
  • one claim-grounding and contradiction route
  • one recommendation-pressure route
  • one downstream consequence or refusal route

If one of those pieces is missing, the family may still be useful, but the sentence has to narrow.

Why DDA Still Works As The Clearest Example

DDA remains the best first family because its packet is easy to inspect as one bounded chain:

  • a flagship benchmark package
  • a companion cross-engine pressure package
  • a real import-backed runtime review lane
  • grounded scientific and comparator pressure
  • recommendation challenge and downgrade routes
  • consequence and follow-up boundaries

It is not the strongest family in every dimension, but it remains the clearest reader-first example of the full pattern.

What This Means In Practice

One serious family packet does not mean:

  • broad proteomics coverage
  • repository-wide readiness
  • decision-grade downstream authority

It means something narrower and still important:

one family can now be challenged from public evidence root to downstream consequence through tracked owner surfaces.

Current Family Reading

family current family packet status main reason the sentence still narrows
dda full bounded public packet runtime remains import_only
dia full bounded public packet library and consequence pressure still narrow the broader sentence
lfq full review-grade packet missingness and transfer pressure still block stronger public language
ptm full bounded public packet localization evidence still outruns consequence confidence
targeted full bounded public packet calibration, interference, and burden still narrow broader certainty
multiplex real packet, internal-support only outsider trust still collapses under stress

Strongest Companion Routes

Boundary

This page explains what one serious family packet now means. It should not be read as a shortcut to broader repository claims than the current family and capability-limit pages can defend.