writing-for-non-engineerslisted

# Owner-Facing Writeups ## When to use Any document a **non-technical owner** will read and act on: a plan presented for approval, a diagnostic writeup, an incident explanation, a proposal, or a "here is what we're building for you" doc. Triggers: "write this up for <owner> to review", "make a plan <owner> can look at", "explain to <owner> what we're doing", or any deliverable where a non-operator's approval or trust is the point. ## Overview The owner (the person who lives with a fleet member but does not operate it) and the operator have opposite needs. Writing one document for both fails both. ## The split-document pattern One file, two clearly separated sections, **owner section first**: ``` # What we're building for <Agent> **<Owner>: this one is for you. <Operator>'s version is below it.** ## <Owner>'s version ... 300-500 words, zero jargon, what they will notice... --- --- ## <Operator>'s version ... full technical detail, architecture, open questions... ``` They should never scroll past architecture to find their part. ## Writing the owner section **Lead with the deal, in one sentence.** > "Ace checks himself constantly. When something breaks, he tells you before you find > it. If he can't fix it, the operator gets it — not you." Everything else elaborates that sentence. **Only list things they have personally experienced.** Voice messages failing, dashboards dead, appointments shifted by a wrong timezone. Never log rotation, cache-read percentage, c