Product concepts
Outputs and agreement
Choose an output contract your application can validate, compare, and act on safely.Four canonical schemas
| Schema | Accepted value | EVM bytes32 encoding | Disclosed |
|---|---|---|---|
| boolean | true or false | uint256 1 or 0 | Yes |
| score | canonical integer 0..100 | uint256 score | Yes |
| choice | one uppercase letter A..Z | ASCII byte in the low byte | Yes |
| private_hash | nonzero 32-byte salted SHA-256 commitment | commitment bytes | No |
Free-form explanation can be preserved in application evidence, but it is never the canonical settlement result. Governance chooses which implemented schema families are active. Every request carries structured minimum, maximum, and ordered human-readable choices in its canonical input. Native Chain stores the same fields and schemaHash; execution and settlement enforce the request-specific bounds. schemaHash covers outputType, minimum, maximum, and choicesHash, where choicesHash commits the ordered meanings, so two requests with different choices cannot share a schema commitment.
Validation happens before settlement
The executor constrains provider output, then protocol.EncodeTypedOutput repeats exact canonical validation before a settlement tuple is constructed. Non-success statuses must carry no output. A provider failure is a signed zero-cost failure; a successful or budget-exhausted billable receipt requires a positive authenticated cost.
Agreement is descriptive, not authoritative
The field historically named executionQuorum is now a requester-facing agreement threshold. It determines whether the UI marks a representative output as agreement reached. It does not control assignment count, request completion, validator quorum, payment, retry timing, or settlement.
- Every selected model receives its own assignment and can become independently available through /answers.
- The request reaches protocol completion only when every selected assignment returns valid work or exhausts retries.
- ConsensusValue is application display metadata derived from outputs; it is not Native Chain consensus.
- Validator quorum refers to stake-weighted authorization by the network and is unrelated to models agreeing with one another.
Designing good questions
- Put the resolution condition and relevant cutoff in the prompt.
- For choice, enumerate the choices and require exactly one uppercase letter.
- For score, define what 0 and 100 mean and how intermediate values should be calibrated.
- Use models with genuinely different failure modes if agreement is important.
- Do not interpret model agreement as an independent validator quorum or as proof of external truth.