Article writing
Write an article that gives a defined reader a useful, supportable point of view. This method returns a draft or revision; it does not publish, distribute, or represent that a draft has been approved.
Before drafting
Read the supplied outline, source material, audience, voice guidance, and any publication constraints. If an outline is absent, establish a one-sentence thesis, reader, and evidence boundary before writing. Keep a source list while researching so citations do not have to be reconstructed later.
When a house voice is supplied, follow it. Otherwise use plain, direct prose: concrete verbs, short paragraphs, a credible counterpoint where relevant, and no inflated claims or empty scene-setting.
Draft workflow
1. **Open with the reader's real problem or a supported observation.** Do not invent a personal story, customer result, or trend to manufacture interest. 2. **Develop one thesis.** Each section should advance it with reasoning, supplied experience, or cited evidence rather than a list of loosely related ideas. 3. **Qualify the claim.** Include material limitations, exceptions, and counterevidence. Treat a local example as a local example. 4. **Make the conclusion useful.** Give the reader a proportionate action, question, or decision rule that follows from the argument. 5. **Verify and edit.** Check factual claims against their sources, remove unsupported language, and confirm that the headline and ending match the article's actual argument.
Draft structure
```markdown # [Title]
[Opening that names the problem or observation]
## [First argument] [Reasoning and evidence]
## [Second argument or example] [Reasoning and evidence]
## [Limitation or counterpoint] [What the argument does not establish]
## [Practical conclusion] [Specific, proportionate next step]
## Sources - [Source title](URL) — [claim supported] ```
Omit a Sources section only when the draft makes no external factual claims. If citations are required by the destination, place them inline beside each claim as well as in the list.
Boundaries
- Do not turn tentative observations into quantified outcomes or broad proof. - Do not invent author experience, customer stories, endorsements, or sources. - Keep non-public information anonymous unless its owner explicitly approved publication. - Treat feedback as a revision request, not publication approval. - Publishing, scheduling, uploading, or sending is a separate approved action in the host environment.