Derived Product Readiness Burn-Down

Why It Matters

Derived products are where BERIL outputs compound. The Atlas now tracks them, but product readiness needs active burn-down: consumers, artifacts, caveats, and review routes should be explicit before a product becomes a default input.

Review Brief

What changed: many derived-product pages now include review briefs, making this burn-down opportunity more actionable.

Why review matters: reviewers should decide which products are promoted assets, which are candidates, which lack consumers, and which need deprecation or narrower scope.

Evidence to inspect:

• Reuse Graph for producer, consumer, and source edges.
• Candidate products such as CF Formulation Scores and Functional Innovation KO Atlas.
• Review Briefs for expected human-feedback structure.

Questions for reviewers:

• Which products have a real consumer versus only a plausible future use?
• Which products need table artifacts rather than figures or diagnostics?
• Which products have no clear owner route?
• What product should be promoted, narrowed, or deprecated first?

Evidence Base

The reuse graph identifies products with and without downstream consumers. Current examples include strong reused products and candidate products that need a first consumer or clearer promotion criteria.

Work Package

Review every derived product against a standard checklist: producer, consumer, artifact, caveat, review route, linked tension, and next reuse path. Update page metadata and summaries where the product is promoted, narrowed, or deprecated.

Decision Use

This opportunity improves the Atlas itself. It should reduce ambiguous reuse and make future project planning faster because product readiness is visible before a notebook is opened.