chio finding

chio finding

Publish, discover, verify, and purchase cognition-market findings.

chio finding [OPTIONS] <COMMAND>

• chio finding operator Initialize, serve, or reconcile a single-operator cognition market.
• chio finding package Build a signed cognition-market package from ordinary development files.
• chio finding admit Admit a verified-fix draft through the running local operator.
• chio finding verify-bundle Re-run the Rust reference verifier over a public proof bundle.
• chio finding publish Publish a canonical chio.finding.v1 artifact to the venue index.
• chio finding search Search the venue descriptor index.
• chio finding verify Verify a finding: strict canonical ingress first, then the pinned evidence facet report.
• chio finding buy Purchase a reveal of a published finding.
• chio finding status Inspect the venue-verified portable status proof for one finding.
• chio finding challenge Open a dispute against one admitted finding listing.

chio finding operator

Initialize, serve, or reconcile a single-operator cognition market.

chio finding operator [OPTIONS] <COMMAND>

• chio finding operator init Create a strict local operator profile and its durable stores.
• chio finding operator serve Run the production-composed purchase service from one profile.
• chio finding operator tick Reconcile durable operator work and print current health counters.
• chio finding operator repair-challenge-retention Restore missing signed challenge filings in an offline operator database.
• chio finding operator validate-hosted Validate a hosted profile, its referenced files, and secret references.
• chio finding operator evaluate-canary Evaluate a bounded hosted canary observation and fail on rollback.

chio finding operator init

Create a strict local operator profile and its durable stores.

chio finding operator init [OPTIONS] --directory <DIRECTORY> --repository-root <REPOSITORY_ROOT>

• --directory <DIRECTORY> New or empty deployment directory. Required.
• --listen <LISTEN> HTTP address for the operator service. Default 127.0.0.1:7143.
• --repository-root <REPOSITORY_ROOT> Existing root containing every seller-accessible source repository. Required.
• --buyer-principal <BUYER_PRINCIPAL> Initial buyer principal installed in the profile. Default coding-agent-buyer.
• --buyer-payout <BUYER_PAYOUT> Canonical EVM destination used for initial buyer compensation. Default 0x1111111111111111111111111111111111111111.
• --seller-principal <SELLER_PRINCIPAL> Initial seller principal installed in the profile. Default coding-agent-seller.
• --seller-payout <SELLER_PAYOUT> Canonical EVM destination used for initial seller proceeds. Default 0x2222222222222222222222222222222222222222.

chio finding operator serve

Run the production-composed purchase service from one profile.

chio finding operator serve [OPTIONS] --profile <PROFILE>

• --profile <PROFILE> Strict canonical operator profile created by operator init. Required.

chio finding operator tick

Reconcile durable operator work and print current health counters.

chio finding operator tick [OPTIONS] --profile <PROFILE>

• --profile <PROFILE> Strict canonical operator profile created by operator init. Required.

chio finding operator repair-challenge-retention

Restore missing signed challenge filings in an offline operator database.

chio finding operator repair-challenge-retention [OPTIONS] --database <DATABASE> --bundle <BUNDLE> --receipt <RECEIPT> --receipt-signing-seed-env <RECEIPT_SIGNING_SEED_ENV>

• --database <DATABASE> Existing operator SQLite database. Stop every operator process first. Required.
• --bundle <BUNDLE> Strict canonical repair bundle containing exact signed envelopes. Required.
• --receipt <RECEIPT> New private file receiving the canonical signed repair receipt. Required.
• --receipt-signing-seed-env <RECEIPT_SIGNING_SEED_ENV> Environment variable containing the repair authority’s hex seed. Required.

chio finding operator validate-hosted

Validate a hosted profile, its referenced files, and secret references.

chio finding operator validate-hosted [OPTIONS] --profile <PROFILE>

• --profile <PROFILE> Strict canonical hosted operator profile. Required.

chio finding operator evaluate-canary

Evaluate a bounded hosted canary observation and fail on rollback.

chio finding operator evaluate-canary [OPTIONS] --profile <PROFILE> --observation <OBSERVATION>

• --profile <PROFILE> Strict canonical hosted operator profile. Required.
• --observation <OBSERVATION> Strict canonical audit-authority-signed canary observation. Required.

chio finding package

Build a signed cognition-market package from ordinary development files.

chio finding package [OPTIONS] <COMMAND>

chio finding package verified-fix

Prove a failing baseline and passing candidate, then package their patch.

chio finding package verified-fix [OPTIONS] --profile <PROFILE> --repository <REPOSITORY> --base <BASE> --candidate <CANDIDATE> --test <TESTS> --topic <TOPIC>

• --profile <PROFILE> Strict canonical operator profile. Required.
• --repository <REPOSITORY> Git repository containing both revisions. Required.
• --base <BASE> Baseline commit or revision that must fail at least one test. Required.
• --candidate <CANDIDATE> Candidate commit or revision that must pass every test. Required.
• --test <TESTS> Test command. Repeat this flag to run more than one command. Required.
• --topic <TOPIC> Finding topic used by market discovery. Required.
• --seller <SELLER> Configured seller principal used to sign the Finding. Default coding-agent-seller.
• --price <PRICE> Listing price in USD minor units. Default 300.
• --output <OUTPUT> Output path. Defaults to the profile’s packages directory.

chio finding admit

Admit a verified-fix draft through the running local operator.

chio finding admit [OPTIONS] --profile <PROFILE> --package <PACKAGE>

• --profile <PROFILE> Strict canonical operator profile. Required.
• --package <PACKAGE> Draft emitted by chio finding package verified-fix. Required.

chio finding verify-bundle

Re-run the Rust reference verifier over a public proof bundle.

chio finding verify-bundle [OPTIONS] --input <INPUT> --profile <PROFILE>

• --input <INPUT> Proof bundle file, or - for standard input. Required.
• --profile <PROFILE> Strict canonical operator profile containing public deployment pins. Required.
• --purchase-request <PURCHASE_REQUEST> Exact canonical purchase request to bind to an optional result.
• --purchase-result <PURCHASE_RESULT> Exact canonical purchase result whose signed terminal is verified.

chio finding publish

Publish a canonical chio.finding.v1 artifact to the venue index.

chio finding publish [OPTIONS] --file <FILE>

• --file <FILE> Canonical artifact file. The bytes are sent verbatim; the venue rejects any spelling that is not the canonical serialization. Required.

chio finding search

Search the venue descriptor index.

chio finding search [OPTIONS] --topic-prefix <TOPIC_PREFIX>

• --topic-prefix <TOPIC_PREFIX> Topic prefix to match. Required.
• --context-sha256 <CONTEXT_SHA256> Optional exact context digest filter (64 lowercase hex characters).
• --after <AFTER> Resume after this finding id, using the cursor from a prior page.
• --limit <LIMIT> Maximum number of rows to request. The venue clamps its own bounds.

chio finding verify

Verify a finding: strict canonical ingress first, then the pinned evidence facet report.

chio finding verify [OPTIONS]

• --file <FILE> Local artifact file to verify without contacting a venue.
• --id <ID> Finding id to fetch verbatim from the venue before verifying.
• --evidence <EVIDENCE> Resolved evidence bundle: receipts with inclusion proofs, checkpoints, the collateral allocation snapshot, and an optional exact canonical status proof encoded as base64.
• --recipe <RECIPE> Raw replay-recipe preimage bytes the artifact commits to.
• --status-rollback-floor <STATUS_ROLLBACK_FLOOR> Durable per-feed status rollback floor. Required whenever the evidence bundle carries a portable status proof. This may point to the same floor file used by chio finding status.
• --integrity-only Assert artifact integrity alone and name every facet left unevaluated instead of failing on absent evidence.
• --trust <FILE> Trust file to verify against instead of the default (.chio/trust.toml in the project, then ~/.chio/trust.toml). A trust file beside the input is never read on its own. Reads CHIO_TRUST.

chio finding buy

Purchase a reveal of a published finding.

chio finding buy [OPTIONS] --id <ID> --max-price <MAX_PRICE> --currency <CURRENCY>

• --id <ID> Finding id to purchase. Required.
• --max-price <MAX_PRICE> Maximum acceptable price in minor units of --currency. Required.
• --currency <CURRENCY> Currency the price ceiling is denominated in. Required.
• --payer <PAYER> Buyer principal the purchase context binds.
• --deadline-secs <DEADLINE_SECS> Seconds the buyer allows for delivery before the failed-delivery terminal applies.
• --pool-allocation <FILE> Signed chio.finding.pool-allocation.v1; the purchase is debited from the pool and refused if it would exceed the signed amount.

chio finding status

Inspect the venue-verified portable status proof for one finding.

chio finding status [OPTIONS] --id <ID> --feed <FEED> --operator-authorization <OPERATOR_AUTHORIZATION> --service-bond <SERVICE_BOND> --rollback-floor <ROLLBACK_FLOOR> --max-epoch-age-secs <MAX_EPOCH_AGE_SECS>

• --id <ID> Finding id whose current status proof should be fetched. Required.
• --feed <FEED> Governance-pinned status feed configured by the venue. Required.
• --operator-authorization <OPERATOR_AUTHORIZATION> Governance-pinned status operator authorization (strict canonical JSON). Required.
• --service-bond <SERVICE_BOND> Governance-pinned current status service bond (strict canonical JSON). Required.
• --rollback-floor <ROLLBACK_FLOOR> Durable rollback floor; retain its sibling .retractions directory. Required.
• --max-epoch-age-secs <MAX_EPOCH_AGE_SECS> Maximum accepted age of the signed status epoch in seconds. Required.

chio finding challenge

Open a dispute against one admitted finding listing.

chio finding challenge [OPTIONS] --finding <FINDING> --class <CLASS> --evidence <EVIDENCE>

• --finding <FINDING> Finding id the challenge targets. The venue’s stored artifact is fetched verbatim, re-derived through the strict ingress, and its exact digest is bound into the challenge. Required.
• --class <CLASS> Mechanical evidence class presented. Must name the same class as the evidence union the document carries; the closed guarantee/evidence compatibility matrix is checked against the fetched finding before anything is signed. Required. Values digest-mismatch, evidence-invalid, replay-contradiction.
• --evidence <EVIDENCE> Challenge evidence document (JSON). Strict canonical I-JSON: the file bytes must be exactly their own canonical serialization, and every field is required. The document carries the operator-supplied half of the challenge; the fetched artifact supplies schema, challenge_id, finding_id, and finding_artifact_sha256. Every key below, at every depth, is in canonical order, which is the order the file must use. { "affected_deliveries": [ {"checkpoint_ref": "...", "checkpoint_sha256": "<64 hex>", "receipt_id": "...", "receipt_sha256": "<64 hex>"} ], "authorization": {"buyer_submission": {"challenger": "<64 hex>", "dispute_fee_terminal": {...}, "dispute_lock_ref": {...}, "standing": {"failed_delivery": {...}}}} | {"venue_audit": {"audit_epoch_envelope_sha256": "<64 hex>", "authorization_digest": "<64 hex>", "selection_digest": "<64 hex>"}}, "evidence": {"digest_mismatch": {"deny_checkpoint_ref": {...}, "deny_receipt_ref": {...}, "failed_delivery_envelope_sha256": "<64 hex>"}} | {"evidence_invalid": {"challenged_checkpoint_ref": {...}, "challenged_evidence_receipt_refs": [...], "purchase_record_envelope_sha256": "<64 hex>"}} | {"replay_contradiction": { "purchase_record_envelope_sha256": "<64 hex>", "recipe_preimage": "<canonical recipe text>", "reproduction": [...]}}, "filed_at": 1750000000, "listing": {"backing_envelope_sha256": "<64 hex>", "listing_id": "...", "profile_envelope_sha256": "<64 hex>", "terms_envelope_sha256": "<64 hex>", "venue_admission_envelope_sha256": "<64 hex>"} } Both unions and every branch member use the registered chio.finding.challenge.v1 spelling. Copy the listing block from the venue’s current signed admission envelope. Required.
• --challenger-key <CHALLENGER_KEY> Ed25519 seed file for the challenger the document names: 64 hex characters, optional 0x prefix, surrounding whitespace ignored. Required for a buyer submission, because the signer must be that challenger. Refused for a venue audit, which carries no challenger at all.
• --venue-audit Build the bondless venue-audit branch. The document’s authorization must be the matching branch, so a submission carrying a dispute fee or a dispute bond is refused rather than stripped.
• --dry-run Emit the canonical challenge, the signed envelope when one was produced, and their digests, without transmitting anything.