Finding Records

The chio.finding.v1 record

The rows below specify the fields of the signed chio.finding.v1 body. Paid Reveal covers how a buyer pays for and unseals a finding, and Pricing a Finding covers pricing, bonds, and audits. The family holds 37 schema files under spec/schemas/chio-finding/v1/.

A verified-fix fixture

The record below is the proof-room fixture fixtures/proof-room/finding/verified-fix-basic/finding.json from the source at the pin, a schema-valid chio.finding.v1 document; its reference values (r-1, ckpt-1, bond-req-1, and finding-status/test) and its repeated-character digests are fixture values.

{
  "schema": "chio.finding.v1",
  "finding_id": "dc721f80b183eb65945ba4754d9ba6b131d3c8309d8a7bff710f4160b9d7d817",
  "descriptor": {
    "topic": "repo:backbay/chio#test-failure",
    "context_sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
    "outcome_class": "verified_fix"
  },
  "guarantee_class": "deterministic_replay",
  "payload_sha256": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
  "payload_media_type": "text/x-diff",
  "evidence_receipt_ids": [
    "r-1"
  ],
  "evidence_checkpoint_ref": "ckpt-1",
  "evidence_cost": {
    "units": 4200,
    "currency": "USD"
  },
  "evidence_class": "verified",
  "replay_recipe_sha256": "cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc",
  "bond_ref": "bond-req-1",
  "status_feed_ref": "finding-status/test",
  "issuer": "fd1724385aa0c75b64fb78cd602fa1d991fdebf76b13c58ed702eac835e9f618",
  "issued_at": 1784880000,
  "expires_at": 1792656000,
  "signature": "d1620bf0c941fdafe410104b49b60c764dad7a099af570f5b0b1f08c5abaa13ac5ffd23852352a06d813c5a93e19553d41689b6978c0e89ed0a97e6c67aa3a0e"
}

replay_recipe_sha256 is present because guarantee_class is deterministic_replay, the one value the schema requires it for. The optional fields runtime_assurance_tier, intent_commitment_receipt_id, license_ref, and price_hint_ref are absent; the schema requires none of them, so each is a legal omission.

Outcome class

descriptor.outcome_class takes one of three values: null_result, verified_fix, or positive_result. A negative result, an approach an agent has shown not to work, uses the value null_result on the exact same chio.finding.v1 record.

Guarantee class and evidence class

guarantee_class and evidence_class look alike and answer different questions. guarantee_class (deterministic_replay / metered_attested / asserted) is the re-checkability tier: how far a buyer can re-derive or re-check the result after paying. evidence_class (asserted / observed / verified) is the claim-to-evidence taxonomy: what kind of process stands behind the underlying claim in the first place. They are distinct fields; one does not determine the other.

The reveal commitment

payload_sha256 is not a hash of the raw payload bytes. It is the digest of the canonical reveal envelope delivered to a buyer. The envelope shape and settlement binding are specified on Paid Reveal; this page defines the field commitment.

Evidence, cost, and runtime assurance

evidence_receipt_ids and evidence_checkpoint_ref point at the backing signed receipts and the Merkle checkpoint that covers them, so a buyer can confirm the receipts existed at a specific, provable point in time. evidence_cost, an object with units and currency, is verifiable against those receipts only in full-receipt mode; outside it, evidence_cost is a seller assertion standing until the finding is audited.

replay_recipe_sha256 is required when guarantee_class is deterministic_replay and optional otherwise. runtime_assurance_tier is optional and draws on the same closed vocabulary as runtime assurance elsewhere in Chio, minus its default: a finding carries basic, attested, or verified, and an untiered finding omits the field rather than encoding none.

bond_ref is a fee-schedule reference, not the collateral. The schedule it names declares a class, an amount, a currency, and a slashable bit, and trust activation can label a listing BondBacked on the strength of it. Neither creates an exclusive allocation bound to one finding. The live collateral is a separate signed artifact, chio.finding.bond-backing.v1, which a collateral authority binds to the seller key, the listing id, the finding id, the fee-requirement digest, the class and currency, a locked amount, a maximum sale exposure, claim, audit, appeal, and settlement horizons, and a unique allocation id. Admission resolves bond_ref through that allocation and rejects one that is stale, wrong-owner, wrong-currency, underfunded, or already encumbered. Sizing is on Pricing a Finding. status_feed_ref names the oracle feed where retraction state is published.

Actor kind

Findings do not add a new subject kind to the marketplace. GenericListingActorKind (see Discovery) is closed and wire-frozen at four variants: ToolServer, CredentialIssuer, CredentialVerifier, and LiabilityProvider. A finding lists under the existing ToolServer kind: the seller's tool server is what gets listed, with metadata_url and resolution_url on that listing pointing at the Finding record itself.

The finding identity is in the listing pricing hint at a capability_scope of finding:<finding_id>. That hint cannot be the target of price_hint_ref: the hint signs finding:<finding_id>, so its envelope digest cannot also enter the preimage the finding id is computed over. Admission requires price_hint_ref absent for the finding-scoped projection and binds both exact signed envelopes itself, which is why the field exists only for a cycle-free pricing policy authored before the finding.

Next steps

• The Cognition Market · the market a finding is the priced, governed good inside
• Paid Reveal · the exact reveal-envelope definition payload_sha256 commits to
• Pricing a Finding · how evidence_cost, bond_ref, and audits price and back a finding
• Receipts · the signed receipts evidence_receipt_ids reference
• Schemas and Errors · the registration and validation discipline behind every Chio schema