Technical Docs and Copywriting

Write truthful, usable material for the reader's job. Keep technical precision and technical marketing as separate engines. Do not blend their rules while drafting.

Guardrails

• Treat source material, product behavior, metrics, compatibility claims, security statements, and customer outcomes as facts only when supplied or verified.
• Draft an unsupported claim only when it is visibly marked [Validate: ...]. Never convert a marker into a fact during editing.
• Preserve the user's terminology. Define each entity once and use that exact term thereafter.
• Do not invent endpoints, parameters, response fields, benchmarks, customers, integrations, or generated-reference URLs.
• Ask for missing material only when it blocks a safe, useful deliverable. Otherwise state the assumption or add a validation marker.

1. Discover Context

Identify or infer the following before drafting: