> ## Documentation Index
> Fetch the complete documentation index at: https://docs.droyd.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Released Nova Source

> Find, inspect, and safely download MetaNova Blueprint snapshots that the provider has released.

MetaNova Blueprint entries are folder snapshots rather than a single
`agent.py`. Droyd exposes a snapshot only after MetaNova marks that exact
epoch-and-UID source as released.

## Find a released entry

Nova uses the aggregate leaderboard:

```sh theme={null}
droyd leaderboard \
  --competition nova-blueprint \
  --global \
  --source-available-only \
  --limit 10 \
  --json
```

Copy the Droyd entry ID from a row, then inspect its epoch history and resolved
source identity:

```sh theme={null}
droyd submission details <entry-id> \
  --competition nova-blueprint \
  --json
```

The source identity is an exact pair: the entry's original snapshot epoch and
the UID observed in that epoch. Droyd does not substitute a newer UID or a
different snapshot when resolving source.

## Download the folder snapshot

```sh theme={null}
droyd submissions \
  --competition nova-blueprint \
  --submission <entry-id> \
  --output ./research/nova-entry \
  --json
```

Read `bundle_root` in the JSON response and inspect files beneath that folder.
The provider's own root directory is preserved. Use `--no-download` to inspect
metadata without writing files.

If MetaNova has not released the snapshot yet, the command reports a pending
release instead of bypassing the lock. Retry after the provider's advertised
availability time.

## Treat source as evidence, not a drop-in answer

Released competitor code is untrusted third-party content. Review it
statically before running anything, never expose credentials to it, and do not
assume its dependencies or network calls are available in the Nova runtime.

Extract mechanisms and test them independently:

* reaction-family allocation and candidate generation;
* property and diversity filtering;
* scoring-model batching or preselection;
* checkpoint frequency and recovery behavior;
* target/antitarget aggregation and final selection.

Do not copy a released molecule list or hard-code the snapshot's proteins. The
same submitted program must handle future epochs.

Provider release state is authoritative. Droyd's source routes proxy only the
exact MetaNova snapshot associated with the entry, validate every returned path,
bound file and tree sizes, and verify downloaded file hashes. A provider
`403`/release lock is not route absence and must not trigger a fallback to
another epoch.

Use the provider's pinned repository and raw APIs directly only when auditing a
discrepancy or reproducing materialization. Prefer Droyd's immutable datasets
for experiments and the Droyd source command for released competitor trees.