R/retain_study_terrain_evidence.R
retain_study_terrain_evidence.RdCopies one explicitly selected local metadata or processing-record file into the linked terrain manifest's folder and records its SHA-256 in a new context. Files are never fetched, parsed, executed, or treated as verified lineage.
retain_study_terrain_evidence(
dsn,
output_file,
evidence_id,
association_id,
source_file,
kind,
description,
source_reference,
qualifications,
analyst,
report_file = NULL,
report_purpose = "definition"
)Existing Study Area context with a terrain source-use account.
New context .gpkg beside dsn.
New caller-supplied local evidence ID; records are append-only.
Existing source-use claim ID to which this evidence applies.
Existing local file selected by the analyst. Originals are unchanged. Select only material suitable for the project's access controls; do not attach credentials, restricted material or unnecessary personal data.
METADATA_SNAPSHOT or PROCESSING_RECORD. A processing record is supplied documentation, not proof of execution or an executable recipe.
Human-readable description of the selected evidence.
Original location/reference and known edition/date. This text is not fetched; the retention timestamp is not an acquisition date.
Explicit limitations and relevance to the claim.
Recorder attribution, not approval.
Optional new HTML report path.
definition (default), terrain, or staging.
List of context and report paths. Schema 4 retains relative paths and fingerprints; move the complete folder. Fresh reports distinguish matching, missing, changed and unreadable attachments without promoting source use. A failure after file publication may retain an unreferenced copy; retry reuses identical bytes. A later report failure retains the context. No multi-file transaction, digital signature, exact source-product inventory or processing execution verification is provided. Earlier snapshots are never replaced.