# Biomol External Validation Preparation

## Purpose

Prepare one external non-AdK trajectory test after v1.4 public-language and result-page polish are complete.

## Why this matters

Most MD Evidence tests so far used public AdK-derived validation packages. The next credibility step is an external trajectory that was not generated from the internal benchmark pipeline.

## Required preparation

- identify external trajectory source
- confirm license and public suitability
- confirm topology and trajectory formats
- estimate upload size
- confirm whether the format path is already supported
- prepare metadata file
- run through protected pilot-key upload
- create MD Evidence result
- download evidence bundle
- document successful parse or failure mode

## Preferred external trajectory characteristics

- public or permission-cleared
- small-to-medium file size
- compatible topology/trajectory pair
- non-AdK protein/system
- scientifically recognizable enough for reviewer discussion
- no confidential or unpublished researcher data

## Expected output

- protected MD Evidence result
- parser status
- frame/atom/residue counts
- RMSD/RMSF/radius-of-gyration summaries when parseable
- evidence bundle
- manifest
- checksum file
- validation note

## Failure handling

If parsing fails, the result should still document:

- file identity
- hash
- parser error
- compatibility limitation
- recommended next step

A clear failure case is valuable because it demonstrates honest boundaries and compatibility behavior.