# Data management plan

## Evidence classes

1. `SIMULATED`: deterministic local-coordinate mission, capture manifest, DN arrays, relative-reflectance arrays, maps, tests, figures and receipts created by this package.
2. `PUBLIC_METADATA_ONLY`: citations and licence facts for DJI documents, scholarly articles and candidate open datasets. No third-party raw file is included.
3. `PUBLIC_DERIVED_THIRD_PARTY`: v1.1 downloads four Atherton et al. Mavic 3M spectral-response CSV files from Zenodo 11102543 into memory, verifies their registered SHA-256 values, and publishes only attributed response summaries and a derivative figure under the source CC BY 4.0 terms. The raw CSV files are not stored or repackaged.
4. `FUTURE_FIELD`: real Mavic 3M imagery, exact coordinates, landholder records, airspace checks and ground observations. None exists in v1.0 or v1.1.

## Public/private boundary

The publishable candidate package may contain source code, tests, synthetic outputs, derived summaries, original figures and source links. It also contains an unmodified Noto Sans TC font solely for reproducible searchable-PDF generation, together with its SIL Open Font License 1.1 notice. The font is not covered by CC BY 4.0. The package must not contain private field coordinates, names, phone numbers, addresses, aircraft credentials, flight-application records, third-party manuals, scraped full text or third-party raw imagery.

If a later field pilot is authorized, precise coordinates, original EXIF, landholder identity and consent forms remain in access-controlled storage. Any public field geometry must be displaced or generalized and reviewed against re-identification risk.

## Reproducibility

The canonical demo seed is `20260804`. `python run_demo.py` creates the mission receipt, 408 capture-event rows, quality-control summary, compressed synthetic arrays, system-analysis record and four figures. A clean rerun must reproduce selected machine-readable files byte for byte. `python run_focused_analysis.py` separately creates the measured-response receipt, 35-scenario mission envelope and two revision figures; it fails closed if a third-party source hash changes. The remote download makes this second step network-dependent, so a publication receipt must record the successful source hashes and run date.

## Retention and correction

The public v1.0 and v1.1 releases are represented by separate immutable archives, checksums and version DOIs under concept DOI `10.5281/zenodo.21789963`. Version 1.0 remains at DOI `10.5281/zenodo.21789964`; version 1.1 is identified by DOI `10.5281/zenodo.21791470`. Corrections must create a new version and preserve prior public versions rather than silently replace them.

