Lexicon Garden

app.matakite.resolution

An outcome determination for a question. Resolution is data, not authority: any DID can write one, and appviews choose which resolvers to trust and display (default: the question's designated resolver). Outcome semantics follow Metaculus: 'ambiguous' = reality could not be determined under the criteria; 'annulled' = the question itself was defective (underspecified, assumptions violated). Both are excluded from forecaster Brier scoring; 'annulled' counts against the question author's quality record.

Repository @matakite.app did:plc:vhycfha6sjn44hxepb5bmjax namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritymatakite.app
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

createdAt

requiredstring · datetime

evidence

array

Sources supporting the outcome, captured at resolution time. Archive links encouraged; sources rot.

  • maxLength: 10
itemsref
Reference

note

string

Optional reasoning, especially recommended for ambiguous/annulled outcomes.

  • maxLength: 3000
  • maxGraphemes: 300

outcome

requiredstring

Semantic outcome. For binary questions this is the resolved value. For non-binary questions a 'yes' outcome pairs with a typed value field (resolvedOption for multi, resolvedValue for numeric, resolvedDate for date); 'ambiguous'/'annulled' apply to every question type and carry no typed value.

  • knownValues: yes | no | ambiguous | annulled

resolvedDate

string · datetime

For a date question, the UTC datetime the event occurred, within the question's date bounds. Optional and only meaningful for date resolutions. Additive per scoring-spec v0.3 §1.

resolvedOption

string

For a mutually exclusive multi question (sumToOne), the stable option id from the subject question's multi.optionIds that resolved yes. Optional and only meaningful for multi resolutions; ignored for other question types. Additive per scoring-spec v0.3 §1.

  • minLength: 1
  • maxLength: 640
  • minGraphemes: 1
  • maxGraphemes: 64

resolvedValue

string

For a numeric question, the decimal-string value the question resolved to, within the question's numeric bounds. Optional and only meaningful for numeric resolutions. Additive per scoring-spec v0.3 §1.

subject

requiredref

The question being resolved (uri + cid). The cid pins the question version the outcome applies to.

Reference

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • app.matakite.question

    record

    A resolvable forecasting question. Immutability contract: editing this record after forecasts exist changes its CID; forecasts reference the question by strongRef (uri+cid), so appviews detect and flag post-forecast edits.

  • app.matakite.dispute

    record

    A public counter-attestation against a resolution. With no bonds available (no money), the deterrent is reputational: disputes are signed records attached to the disputer's DID, so frivolous disputes cost the disputer. Disputes feed resolver track records ('N resolutions, M disputed, K upheld') that appviews surface when applying trust policies.