app.matakite.resolution
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"main": {
"description": "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.",
"key": "tid",
"record": {
"properties": {
"createdAt": {
"format": "datetime",
"type": "string"
},
"evidence": {
"description": "Sources supporting the outcome, captured at resolution time. Archive links encouraged; sources rot.",
"items": {
"ref": "app.matakite.question#source",
"type": "ref"
},
"maxLength": 10,
"type": "array"
},
"note": {
"description": "Optional reasoning, especially recommended for ambiguous/annulled outcomes.",
"maxGraphemes": 300,
"maxLength": 3000,
"type": "string"
},
"outcome": {
"description": "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"
],
"type": "string"
},
"resolvedDate": {
"description": "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.",
"format": "datetime",
"type": "string"
},
"resolvedOption": {
"description": "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.",
"maxGraphemes": 64,
"maxLength": 640,
"minGraphemes": 1,
"minLength": 1,
"type": "string"
},
"resolvedValue": {
"description": "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.",
"type": "string"
},
"subject": {
"description": "The question being resolved (uri + cid). The cid pins the question version the outcome applies to.",
"ref": "com.atproto.repo.strongRef",
"type": "ref"
}
},
"required": [
"subject",
"outcome",
"createdAt"
],
"type": "object"
},
"type": "record"
}
},
"id": "app.matakite.resolution",
"lexicon": 1
}
Metadata
- DID
-
did:plc:vhycfha6sjn44hxepb5bmjax - CID
-
bafyreidrryqi5l3ab4va7z3h7u5m443ycwru3sbc2v4sd245j74hs6jggy - Indexed At
- 2026-07-11 20:53 UTC
- AT-URI
-
at://did:plc:vhycfha6sjn44hxepb5bmjax/com.atproto.lexicon.schema/app.matakite.resolution
Referenced Schemas (1)
Similar Lexicons
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 edi…
-
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. …