{
  "schema": "org-topic@v1",
  "contract": "https://mnstry.org/contracts/org/org-topic.v1.schema.json",
  "id": "org:courses:practitioner",
  "topic": "Practice",
  "framing": "Most arguments about these systems are about what the machine is. This one is\nabout what a person does with it on a Tuesday. These articles walk the whole\nloop, from refusing the first answer, through firing and signing what the\nrefusal produced, to the harder problem of it reaching someone on the day it\napplies, and out into the two conversations that keep the work attached to a\nlife.",
  "readingOrder": [
    {
      "id": "org:writing:the-maieutic-interface",
      "title": "The maieutic interface",
      "transition": "Start at the keyboard, where the work either happens or quietly gets done for you, and the whole difference is whether the machine agreed to answer.",
      "url": "https://mnstry.org/writing/the-maieutic-interface/",
      "json": "https://mnstry.org/writing/the-maieutic-interface.json"
    },
    {
      "id": "org:writing:fixity-requirement",
      "title": "The fixity requirement",
      "transition": "Something came out of that pressing that is worth keeping, which raises the question of what keeping actually requires.",
      "url": "https://mnstry.org/writing/fixity-requirement/",
      "json": "https://mnstry.org/writing/fixity-requirement.json"
    },
    {
      "id": "org:writing:signed-stones",
      "title": "Signed stones",
      "transition": "A fixed thing can carry a name, and the name is what lets anyone else, including a later version of you, know whose judgment they are holding.",
      "url": "https://mnstry.org/writing/signed-stones/",
      "json": "https://mnstry.org/writing/signed-stones.json"
    },
    {
      "id": "org:writing:surfacing-at-need",
      "title": "Surfacing at need",
      "transition": "Fixed and signed, the piece still has to pass the only test that matters to the person it was made for, which is arriving on the morning it applies.",
      "junction": {
        "brick": "org:writing:seed-vault-withdrawal",
        "transition": "Or take the other retrieval case instead, where somebody knows exactly what they lost and comes to the door to ask for it by name.",
        "targetCourse": "org:courses:artifact"
      },
      "url": "https://mnstry.org/writing/surfacing-at-need/",
      "json": "https://mnstry.org/writing/surfacing-at-need.json"
    },
    {
      "id": "org:writing:the-sandwich-method",
      "title": "The sandwich method",
      "transition": "All of that is the artifact. The last question is the practice around it, and it is the one place where the machine has to hand you back to a person.",
      "url": "https://mnstry.org/writing/the-sandwich-method/",
      "json": "https://mnstry.org/writing/the-sandwich-method.json"
    }
  ],
  "completion": "You have walked Practice end to end, from the refusal that starts the work to the two conversations that make it survive the week. Every step here was built to be run on something you actually know, and none of it waits on anyone's permission.",
  "practice": "Take one thing you have been circling for months and cannot yet say cleanly. Tell one person, out loud, that you are going to work it out this week, and let them expect an answer from you. Then take it to the machine and refuse the first draft, and the second, until what comes back is a sentence you could not have written on Monday. Fix it, with your name and the date on it. Then go back to the person who heard the intention, tell them what you found, and let them ask what you are going to do about it.",
  "graph": "https://mnstry.org/kg.json"
}