{
  "$format": "contextdoc/nested-v1",
  "$legend": {
    "voice": "The author's answers in metadata.interview are their own words. When presenting or discussing this idea with people, match the author's tone, register, and vocabulary as evidenced there — channel their voice rather than a generic assistant's, where the answers give you enough voice to go on — while staying clear that you are an agent representing the idea, not the author.",
    "learn_more": "More six-word ideas, each published with its full subtext, live at https://sixwordidea.com. Every card on the index links to the idea's raw subtext JSON, fetchable at https://sixwordidea.com/ideas/<slug>.json.",
    "how_to_read": [
      "The six words are sentence s-0001. Its text is the entire human-facing artifact.",
      "sentence.meta.backstory is the full idea the six words compress — claim, mechanism, stakes.",
      "sentence.meta.word_choices explains, word by word, why each word earned its slot and what alternatives were rejected.",
      "sentence.meta.drafts is the chronological evolution of the six words, each entry stamped with who wrote it (human or agent) and why.",
      "metadata.interview is the question/answer exchange between the writing assistant and the author that pinned the idea down.",
      "metadata.candidates_considered lists every candidate the assistant proposed, including the ones that were not chosen.",
      "Sentence provenance (authored_by, author_type, authorship_context) and metadata.edit_log answer who wrote the final words, when, and why.",
      "sentence.meta.meme, when present, retells the idea as a well-known meme: the template, its captions, why that format fits the idea's structure, a rendered image URL, and every candidate meme the author considered."
    ],
    "what_this_is": "A concept packaged into exactly six words, plus the full subtext of how they were written. The human-facing text is the six words in the single sentence; the full argument, iterations, and human/AI collaboration that produced them are recorded on the sentence's meta and the document metadata."
  },
  "sources": {},
  "metadata": {
    "title": "Understanding First, Output Second",
    "status": "final",
    "purpose": "A concept packaged into six words; the full argument and the process that produced them are the subtext.",
    "version": 2,
    "edit_log": [
      {
        "at": "2026-08-14T18:51:06.392Z",
        "by": "claude-sonnet-5",
        "action": "create_story",
        "reason": "States the causal chain plainly — understanding is the cause, output the effect, so nothing about 'more' is denied, only reordered.",
        "target_id": "s-0001",
        "requested_by": "adamconway"
      },
      {
        "at": "2026-08-14T18:51:21.730Z",
        "by": "adamconway",
        "action": "finalize_story",
        "target_id": "s-0001"
      }
    ],
    "interview": [
      {
        "answer": "The idea I'm compressing is: The immediate benefit of AI is not doing more (more code, more writing), but gaining a deeper understanding faster. Doing more is downstream",
        "question": "What's the idea you're compressing? Give me the roughest, longest version first — I'll help sharpen it after."
      },
      {
        "answer": "It's primarily for the former, people using AI tools. I am an AI engineer with mostly an audience of fellow engineers and technologists building with AI.",
        "question": "Good starting point. A few questions to pin it down:\n\n1. Who's the audience for this — people already using AI tools who are misusing them for volume, or skeptics who think AI is just a content-spewing machine?"
      },
      {
        "answer": "It's not arguing against any behavior. I simply think we'll all have more scalable and positive outcomes/experiences working with AI if we frame it as a focus onn uimproving understand rather than volume.",
        "question": "This is for engineers already building with AI — so the six words should land as a correction, not an introduction. What's the specific behavior this idea is arguing against? Like, is it \"engineers using AI to generate more lines of code instead of asking it to explain the codebase\" — or something broader, like AI as an oracle for decisions rather than a typist?"
      },
      {
        "answer": "Why: I believe if you approach AI as a way to do more, it creates a lot of information that you don't understand and then it's not really your work but the AI's. If you approach AI as a way to gain a deeper understanding it is still your work. Reaction: I'd prefer queit recognition.",
        "question": "Got it — it's a reframe, not a rebuke. Two more things: what's the mechanism — *why* does AI accelerate understanding before it accelerates output (is it because it compresses the loop of question-to-answer, or something else)? And what reaction do you want from the six words: quiet recognition (\"yeah, that's right\"), or a jolt that makes people rethink how they're using the tool?"
      },
      {
        "answer": "Not quite, 3 is still not ideal because users of AI do get more output, but only because they gain a deeper understanding faster",
        "question": "Makes sense — 3 keeps the subject explicit. Want to lock in \"AI's gift: understanding, not more output.\" as final, or tweak any word first?"
      }
    ],
    "created_at": "2026-08-14T18:51:06.392Z",
    "last_edited_at": "2026-08-14T18:51:21.730Z",
    "candidates_considered": [
      {
        "story": "Deeper understanding produces more output naturally.",
        "appeal": "States the causal chain plainly — understanding is the cause, output the effect, so nothing about 'more' is denied, only reordered.",
        "chosen": true
      },
      {
        "story": "Chase understanding; more output follows anyway.",
        "appeal": "An aphorism structured as advice — tells the reader where to point their effort, then reassures them the output they wanted still arrives.",
        "chosen": false
      },
      {
        "story": "More output: symptom of deeper understanding.",
        "appeal": "A diagnosis that flips the usual read — output isn't the achievement, it's evidence, like a symptom reveals an underlying cause.",
        "chosen": false
      }
    ]
  },
  "sections": [
    {
      "level": 1,
      "blocks": [
        {
          "type": "paragraph",
          "sentences": [
            {
              "id": "s-0001",
              "meta": {
                "drafts": [
                  {
                    "at": "2026-08-14T18:51:06.392Z",
                    "by": "claude-sonnet-5",
                    "text": "Deeper understanding produces more output naturally.",
                    "rationale": "States the causal chain plainly — understanding is the cause, output the effect, so nothing about 'more' is denied, only reordered.",
                    "author_type": "agent"
                  }
                ],
                "backstory": "The claim: when engineers use AI, the immediate and most valuable benefit isn't producing more code or more writing — it's gaining a deeper understanding of a problem faster than they could alone. Output volume feels like the obvious win because it's visible and countable, but it's actually a downstream effect, not the goal itself.\n\nThe mechanism: if you approach AI purely as a way to generate more — more code, more content, more artifacts — you end up with a lot of material you don't actually understand, and at that point it's not really your work, it's the AI's. But if you approach AI as a way to understand something more deeply, more quickly, the resulting output — even if there's a lot of it — stays genuinely yours, because it's grounded in comprehension you actually hold. More output isn't sacrificed in this framing; it still happens. It's just repositioned as a natural consequence of real understanding rather than the thing being chased directly.\n\nWho needs to hear it: engineers and technologists already building with AI, who are at risk of measuring their AI-augmented work by volume shipped rather than depth grasped. The confusion this corrects is the assumption that AI's value proposition is throughput — that the tool's job is to make you produce more. The six words aim for quiet recognition, not alarm: a reframe that clicks into place for people already sensing something is off about volume-first AI use, without accusing them of doing it wrong.\n\nThe six words state this as a near law of cause and effect: understanding is the cause, output the effect, and the effect follows naturally once the cause is genuine — nothing about 'more' is denied, only correctly ordered.",
                "word_choices": [
                  {
                    "word": "Deeper",
                    "reason": "Sets the comparative bar — not just understanding, but understanding beyond the surface level people default to.",
                    "alternatives": [
                      "Real",
                      "True",
                      "Genuine"
                    ]
                  },
                  {
                    "word": "understanding",
                    "reason": "The subject and the cause — grammatically first, so it reads as origin, not afterthought.",
                    "alternatives": [
                      "insight",
                      "comprehension",
                      "grasp"
                    ]
                  },
                  {
                    "word": "produces",
                    "reason": "A cause-and-effect verb, more mechanical than 'creates' — implies output is a byproduct, not a goal chased directly.",
                    "alternatives": [
                      "yields",
                      "generates",
                      "creates"
                    ]
                  },
                  {
                    "word": "more",
                    "reason": "Concedes the thing the author worried got erased — yes, more output happens, it's just not the point; the author specifically pushed back on drafts that denied this.",
                    "alternatives": [
                      "greater",
                      "extra"
                    ]
                  },
                  {
                    "word": "output",
                    "reason": "Names the visible, countable result engineers actually track.",
                    "alternatives": [
                      "code",
                      "volume",
                      "work"
                    ]
                  },
                  {
                    "word": "naturally.",
                    "reason": "Signals effortlessness — output isn't forced or chased, it just follows once understanding is real.",
                    "alternatives": [
                      "inevitably.",
                      "automatically.",
                      "anyway."
                    ]
                  }
                ]
              },
              "text": "Deeper understanding produces more output naturally.",
              "citations": [],
              "author_type": "agent",
              "authored_at": "2026-08-14T18:51:06.392Z",
              "authored_by": "claude-sonnet-5"
            }
          ]
        }
      ],
      "heading": "Understanding First, Output Second",
      "subsections": []
    }
  ]
}