Systematic Model Release Workbench
Review a model as a versioned decision system: data identity, entry objective, exit ownership, reserved evaluation and durable operational state.
Your evidence states are not a provider score, audit opinion or performance finding.

Primary reference documents
References support source definitions and mechanisms, not a completed review, measured return or endorsement. The questions are this publication's editorial record design.
Model-card evidence before a release conclusion
Attach the identified entry objective, source availability, transformation scope, label ownership and independent master to the corresponding evidence fields. A clear card is a specification; only actual artifacts can document research completion. Manually selecting documented does not authenticate a source or make it independent. Imported records retain their own site and check identities to prevent mixing incompatible forms. Preserve a missing reference as unresolved rather than adding a placeholder URL that appears authoritative. The workbench is a reader's collection of evidence questions, not a financial certification engine.
A release chain must survive machine shutdown
Production data refreshes, publishers, schedulers and verification belong in managed cloud services. A local test or manual deployment is not an ongoing production dependency. An actual model release needs its cloud artifact and subscriber route distinct from a research LIVE label or source file present on a branch. This static site edition deploys no new model, creates no local scheduler and purchases no capacity. The browser workbench runs locally for the visitor because it is an educational form, not a production model pipeline.