Derived Data Reuse Graph

Why This Page Exists

The Atlas should make reusable project outputs visible before they become institutional memory. A project output becomes valuable when it can be named, reviewed, reused, and caveated without rereading the full notebook chain.

What The Graph Tracks

• Producing projects and downstream consumers.
• Derived products such as scores, labels, rankings, profiles, candidate lists, and atlas tables.
• Output artifacts that give a human or agent a concrete starting point.
• Collections that feed the product.
• Review routes based on explicit project ownership.
• Tensions that should travel with reuse.

How To Use It

Start with products that have consumers when you need stable reusable inputs. Start with products without consumers when planning the next high-leverage project. Start with products that have unresolved tensions when designing validation work. Start with opportunities when you want to see which product needs a first consumer, readiness burn-down, or validation analysis.

Maintenance Rule

Agents should not silently promote every project output. Promotion requires a named product, at least one producing project, at least one artifact or external location, caveats, and a review route.