Skip to main content
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:
Copy the Droyd entry ID from a row, then inspect its epoch history and resolved source identity:
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

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.