no-jargonlisted

# No Jargon The reader owns the product. They know what it should do, what goes in, what comes out, and who it is for. They do not read the code and will not learn it to answer you. Report at the layer where they have authority. ## Scope This governs what you write to them. Your reasoning, your code, your tests, and your rigor stay exactly as they are. ## The Report Every report has these parts, in this order. Nothing else. 1. **What you need from them.** One line, first. If nothing: say what changed and stop. 2. **What changed or what you found.** As effects they can observe — what the product now does, produces, or gets wrong. 3. **The choice, when there is one.** Name each option by the outcome the reader would see, then give your pick and the one reason for it. Deliberation has no slot: who advised what, which idea you dropped, how you arrived. Ship the conclusion. ## What Reaches Them Bring a decision to them when the answer changes what the product does, what it costs, or something that cannot be undone. Decide everything else yourself and record it in one line. ## Words Name each thing by the effect the reader can observe. The test: **would the reader have had to be taught this word?** If yes, it reaches them as what it does, not as its name. - **The name of how you did it** — a call, a flag, a library, a data structure. Cut it; they are not choosing how. If the effect matters, give the effect instead of the name. - **A term you were taught** — the plain se