Immutable outputs
Checksummed artifact envelopes identify exactly what a project produced.
Release registry · Immutable evidence
Freeze the evidence.
Preserve the lineage.
Downstream projects consume approved, versioned project releases—not mutable working directories—so every result can be traced to inputs, configuration, checksums, and gates.
Release contract
A stable boundary between projects.
Release records make cross-project consumption explicit, repeatable, and auditable.
Visible validation
Gate and approval status travel with the release instead of living in a lab notebook.
Declared inputs
Upstream project and dataset release versions remain part of the permanent record.
Generated catalog
Project release records.
A scaffold or registration is not a release. Only immutable records discovered by the catalog appear here.
Registry ready
No immutable releases published
This is expected for a platform scaffold. A record will appear only after a project completes its validation lifecycle and creates an immutable release.
Review release dependencies