Commands and Contracts

The public runtime surface is intentionally smaller than the full internal module tree. In practice it comes down to three things:

• the commands that rebuild tracked evidence and public outputs
• the artifact families those commands are allowed to write
• the stable Python or CLI entrypoints that outside users can rely on

This section explains those contracts without assuming you already know the internal helper modules. It separates the durable runtime promises from the implementation detail behind them.

Start Here

• open CLI surface for the named commands people are expected to use
• open entrypoints and examples for the shortest supported command paths
• open artifact contracts for the checked-in output families the runtime is allowed to write
• open API surface for the durable Python contract boundary
• open data contracts for the governed roots and file locations
• open operator workflows for verify, refresh, and publication paths
• open animal ancient DNA evidence if your real question is about the evidence chain rather than the command surface