Engineering owns docs content; Customer Engineering or Marketing owns customer-ready packaging

Situation

In Ryan 1:1, Peter split docs into two layers and assigned ownership cleanly: (1) the technical content, details, and accuracy IS engineering responsibility — same as QA. If Ryans org helps fine, but not held to it. (2) Making docs customer-ready/pretty is NOT engineerings responsibility — that lives with Ryan or Lindsay; they decide between themselves where it lives, Peter does not care which.

Reasoning

Same accountability discipline as QA. The bug Peter has been fixing for months is engineers shipping things as done without QA or docs, then expecting Ryans org to backfill the gap. By splitting docs into content-vs-packaging Peter preserves engineering accountability for accuracy while not making engineers do graphic design or polish. This also clears the channel for Ryan to invest in tooling (similar to the QA gauntlet he built) without becoming a permanent docs backstop.

Additional Context

Extends D4 from the 2026-05-21 reflection (Engineering owns all QA) to the docs domain. The QBR same week (5/22) listed QA + docs as woefully incomplete and named Peter as the owner of a new Definition of Done that codifies both.

Observed Evidence

Direct quote: "I want to hold engineering responsible for producing the content." + QBR action item explicitly assigned to Peter to write the new Definition of Done.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis