# NMD-VCell v1 external authorization dossier

This dossier is ready for author and institution input. It does not mint a DOI,
approve licences, publish maintainer contact metadata or authorize formal v1.0.

## Current locked state

- Resource release: `v1.0.0-database-resource`
- Interface build: `EA-20260729-15`
- Dossier status: `ready_for_author_institution_input_formal_v1_locked`
- Formal v1.0: `False`
- External gates complete: `0/4`

## Required archives for DOI deposition

- `analysis_core`: `nmd_vcell_database_resource_v0.8.1-v24r1-20260722.tar.gz` · 9677910 bytes · `b88a3b9f1ae44b48d6ea3c2a568626229cc93f94d539b8ea30f55534aae41f36`
- `evidence_atlas_overlay`: `nmd_vcell_research_workbench_overlay_v1.0.0_database_resource_20260728_stage5_65.tar.gz` · 2635952 bytes · `b6d82501ff29ef153184792d18e3b05180d7ee21ebf22a9eeeae1c703862b14f`

## Required external inputs

- `permanent_doi_archive`: pending_external_action — DOI for the unchanged canonical archive
- `institution_approved_data_licence`: pending_institutional_approval — Approved data licence identifier and text
- `approved_code_licence`: pending_institutional_approval — Approved code licence identifier and text
- `final_maintainer_and_institution_metadata`: pending_author_input — Approved maintainer, affiliation and contact metadata

## Files to use

- Deposit manifest: `v1_deposit_manifest.json`
- Deposit file list: `v1_deposit_file_list.tsv`
- Authorization checklist: `v1_authorization_checklist.tsv`
- External-gate input template: `v1_external_gate_input_template.json`
- Licence/maintainer metadata template:
  `v1_licence_maintainer_metadata_template.tsv`
- Validator: `validate_v1_external_gates.py`

## How to complete

1. Deposit the unchanged release layers listed in `v1_deposit_manifest.json`.
2. Fill the DOI, repository and record URL in
   `v1_external_gate_input_template.json`.
3. Fill institution-approved data and code licence identifiers.
4. Fill author-approved maintainer metadata only after it may be public.
5. Set `formal_release_authorization.authorized` to `true` only after the
   author/institution has approved formal v1.0 wording.
6. Run the validator against the completed template and release manifest.

## Boundary

v1.0 is a database and evidence-governance release; it is not a validated disease-prediction or clinical decision-support release.