knowledge-doc-writinglisted

# Knowledge Doc Writing — Turning Self-Study into Diátaxis Four-Type Docs Turn a technical topic (self-study output, conversation transcripts, or raw source material) into **one document with four cleanly separated Diátaxis sections**: tutorial (walks a first-time reader through hands-on use), how-to (guides an already-competent reader through a task), reference (looks up parameters and structure), explanation (What/Why argumentation and trade-off decisions). The four sections never mix — cross-type content is cross-linked, never inlined. **Only write what the material can support.** Use the compass's two questions to route each piece of material to its section; a section with material support gets written fully and stays pure, and a section that can't be supported (often tutorial/how-to, when the topic was researched but never hands-on) is listed as an explicit gap with the condition needed to fill it — **never fabricate, never build an empty shell**. **Default technical context:** enterprise architecture in financial services, Kubernetes / OpenShift, microservices, AI platforms, RHEL + rootless Podman + Quadlet. Draw examples and comparisons from this context first, so the document reads like real work rather than a textbook generality. Declared once here; later sections reference it without restating it. Plain language throughout; keep established terms in English (see S5). ## Output Language Match the language of the user's request, and apply it to *all* user-facing