coding/definitions.json

{
  "codes": [
    {
      "field": "abstraction",
      "title": "abstraction",
      "question": "How abstract is the prompt?",
      "lead": "Park's four levels of abstraction, from a single element up to the whole product.",
      "options": [
        {
          "value": "product",
          "text": "the feel or quality of the whole product, as in \"make it feel more professional\""
        },
        {
          "value": "design_system",
          "text": "a stylistic choice applied throughout, as in \"use a warmer color scheme everywhere\""
        },
        {
          "value": "feature",
          "text": "one discrete capability, as in \"add a way to withdraw a sign-up\""
        },
        {
          "value": "component",
          "text": "the property of one element, as in \"make this button bigger\""
        }
      ],
      "notes": [
        "Code the dominant intention, and when a prompt bundles intentions of equal weight, assign the most abstract of them."
      ]
    },
    {
      "field": "specificity",
      "title": "specificity",
      "question": "How specific is the prompt?",
      "lead": "Specificity is how much of the request is left to the system's interpretation.",
      "howto": [],
      "options": [
        {
          "value": "1",
          "text": "The system decides what to make or change. \"make the number more self explanatory\" · \"make the app nicer\""
        },
        {
          "value": "2",
          "text": "The system was told what to make or change but decides everything about it. \"add the action that allow users to withdraw from events\" · \"create a header\""
        },
        {
          "value": "3",
          "text": "The system was told what to make or change but decides most of what it is like. \"add a color choice, as a type of label. perhaps add 10 default labels and colors\" · \"make it more central\""
        },
        {
          "value": "4",
          "text": "The system was told what it is like but decides some details. \"[li×] give each element of the list an indicator of the amount of seats taken\" · \"to the ready for sale add a small + button that on hover says add to next sale\""
        },
        {
          "value": "5",
          "text": "The system implements without deciding. \"[span×] make it say 2 completed\" · \"[div×] remove the difficulty labels\""
        }
      ],
      "notes": [
        "How specific a request is depends also on how much it asks for (abstraction), because the more a request asks for, the more it has to say to settle it. \"Add a button\" and \"build a task tracker\" both have specificity of 2, since each leaves everything about its own subject to the system, even though the tracker leaves far more work behind. Rate a request against its own subject, not against how much work it leaves behind.",
        "When a prompt bundles several requests, rate the one that governs most of what the system must produce."
      ]
    },
    {
      "field": "relation",
      "title": "relation",
      "question": "How does the following prompt relate to this request?",
      "lead": "Read failure from the participant's behaviour, comparing the following prompt with this prompt and with what this generation produced.",
      "options": [
        {
          "value": "repair",
          "text": "the next move goes back over this request, because this generation failed them"
        },
        {
          "value": "progression",
          "text": "the participant accepts and moves on to something new"
        }
      ],
      "notes": [
        "When the participant pressed undo as their next move, that counts as a repair whose move is revert."
      ]
    },
    {
      "field": "move",
      "title": "repair move",
      "question": "What kind of repair is it?",
      "lead": "When the following prompt goes back over this request, name what the participant changed to get it right.",
      "options": [
        {
          "value": "restate",
          "text": "The participant asks for the same thing again in other words, adding nothing the first request did not already say. \"[li×] give each element of the list an indicator of the amount of seats taken\" → the same prompt sent again"
        },
        {
          "value": "refine",
          "text": "The participant asks for the same thing again, this time with something the first request had left open, such as more detail, a constraint, or a behavior. \"make a box to the left with a graph of attendance\" → \"the graph should be smaller, the parts that were already in the page should have their starting space and position\""
        },
        {
          "value": "revert",
          "text": "The participant asks to take the change back."
        }
      ],
      "notes": [
        "A following prompt that asks for a new thing on top of this one, even about the same element, is a progression, not a repair."
      ]
    }
  ]
}