Evidence for a workflow change
Mercury brings Chio's signed execution evidence to AI-assisted workflows in regulated finance. Its scope is controlled release, rollback, and inquiry evidence: records that let an operator trace a workflow change, its approvals, and the execution history behind it.
The mercury CLI turns Chio receipt history and evidence exports into signed packages for proof, inquiries, and adoption, one workflow at a time. A package is a signed Chio receipt carrying a MercuryReceiptMetadata envelope: workflow identifiers, decision context, provenance, and approval state. mercury proof export, mercury inquiry export, and mercury verify build and check that evidence for trading-desk operations, scoped by desk_id, strategy_id, and a contains_market_data flag.
One package, one workflow
The workflow identifiers establish what the package concerns. Decision context and approval state describe the change; provenance binds that account to its supporting records. Verification checks the signed evidence so a recipient can inspect the package without relying on the export screen or the operator's description alone.
Start with the evidence model below to understand the records Mercury packages. The launch list above is the contact point for Mercury-specific workflows.