External gate checklist

Formal v1 unlock blockers

All remaining blockers are external authorization fields.

This page lists the exact DOI, licence, maintainer/contact and final authorization fields required before database-v1 wording can be unlocked. v1.0 is a database and evidence-governance release; it is not a validated disease-prediction or clinical decision-support release.

Read checklist JSON Download checklist TSV Open fillable template

Current state16 external fields remain blocking; 2 boundary fields are already constrained. This page does not unlock formal v1.0.

Summary

What must change before formal v1.0?

Total checklist fields18

External blocking fields16

Boundary fields constrained2

Formal v1.0LOCKED

Field-level checklist

Fill only after external approval

Field	Owner	Expected value	Current value	Status
`deposit.repository`	repository_or_author	nonempty repository name	empty	missing_or_blocking
`deposit.doi`	repository_or_author	minted DOI, format 10.xxxx/xxxxx	empty	missing_or_blocking
`deposit.record_url`	repository_or_author	public DOI record URL	empty	missing_or_blocking
`data_licence.identifier`	institution	institution-approved identifier	empty	missing_or_blocking
`data_licence.approval_status`	institution	institution_approved	pending_institutional_approval	missing_or_blocking
`data_licence.approval_reference`	institution	nonempty approval or policy reference	empty	missing_or_blocking
`code_licence.identifier`	institution	institution-approved or SPDX identifier	empty	missing_or_blocking
`code_licence.approval_status`	institution	institution_approved	pending_institutional_approval	missing_or_blocking
`code_licence.approval_reference`	institution	nonempty approval or policy reference	empty	missing_or_blocking
`maintainer.name`	author	public maintainer name	empty	missing_or_blocking
`maintainer.institution`	author	public maintainer institution	empty	missing_or_blocking
`maintainer.email`	author	valid public contact email	empty	missing_or_blocking
`maintainer.approval_status`	author	author_approved	pending_author_input	missing_or_blocking
`formal_release_authorization.authorized`	author_and_institution	true only after all external gates pass	false	missing_or_blocking
`formal_release_authorization.approved_by`	author_and_institution	final approver name	empty	missing_or_blocking
`formal_release_authorization.approved_at`	author_and_institution	ISO-8601 timestamp	empty	missing_or_blocking
`database_only_claim_boundary_confirmed`	resource_governance	true	true	preconfirmed_boundary
`disease_prediction_platform_claim_expansion`	resource_governance	false	false	preconfirmed_no_expansion

Input files

Use these files, in this order

Confirm the v1 deposit view.
Fill the external gate input JSON.
Fill licence/maintainer metadata TSV.
Run the strict validator.
Only after all checks pass, ask for explicit formal release authorization.

Non-automated actions

What Codex/site cannot do

Mint a DOI or repository record.
Grant institution-approved data or code licences.
Approve public maintainer/contact metadata.
Authorize formal v1.0 wording.
Convert database-resource status into a disease-prediction claim.

Validator command

Run from the public resource root after filling the template:

python3 downloads/validate_v1_external_gates.py downloads/v1_external_gate_input_template.json --manifest api/v1.1/release_manifest.json

Successful structural validation still does not grant institutional approval, publish private metadata, deploy the website or change scientific claims.

Open v1 authorization dossier · Open v1 release gate · Open QA status