app.matakite.resolution

matakite.app

Documentation

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.

main record

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.

Record Key tid Timestamp-based ID

Properties

createdAt string datetime Required

An RFC 3339 formatted timestamp.

evidence array of ref app.matakite.question#source Optional

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

maxLength: 10 items
note string Optional

Optional reasoning, especially recommended for ambiguous/annulled outcomes.

maxLength: 3000 bytesmaxGraphemes: 300 graphemes
outcome string Required

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.

Known values: yes, no, ambiguous, annulled
resolvedDate string datetime Optional

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 Optional

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.

maxLength: 640 bytesminLength: 1 bytesmaxGraphemes: 64 graphemesminGraphemes: 1 graphemes
resolvedValue string Optional

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 ref com.atproto.repo.strongRef Required

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

View raw schema 
{
  "key": "tid",
  "type": "record",
  "record": {
    "type": "object",
    "required": [
      "subject",
      "outcome",
      "createdAt"
    ],
    "properties": {
      "note": {
        "type": "string",
        "maxLength": 3000,
        "description": "Optional reasoning, especially recommended for ambiguous/annulled outcomes.",
        "maxGraphemes": 300
      },
      "outcome": {
        "type": "string",
        "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"
        ]
      },
      "subject": {
        "ref": "com.atproto.repo.strongRef",
        "type": "ref",
        "description": "The question being resolved (uri + cid). The cid pins the question version the outcome applies to."
      },
      "evidence": {
        "type": "array",
        "items": {
          "ref": "app.matakite.question#source",
          "type": "ref"
        },
        "maxLength": 10,
        "description": "Sources supporting the outcome, captured at resolution time. Archive links encouraged; sources rot."
      },
      "createdAt": {
        "type": "string",
        "format": "datetime"
      },
      "resolvedDate": {
        "type": "string",
        "format": "datetime",
        "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."
      },
      "resolvedValue": {
        "type": "string",
        "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."
      },
      "resolvedOption": {
        "type": "string",
        "maxLength": 640,
        "minLength": 1,
        "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,
        "minGraphemes": 1
      }
    }
  },
  "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."
}

Lexicon Garden

@