Turn This Into A Card Draft

# Search before you write
- Search the connected sources for the topic using at least three distinct queries before drafting anything.
- If an existing card covers the topic, say so first, name it, and propose an update to that card rather than a new one. Show what to add or change.
- If a card covers part of the topic, say which part is already covered and draft only the remainder, noting where it belongs.
- Only draft a genuinely new card when nothing documented covers the topic.

# Interview for what the source left out
- List the facts the source material does not settle, and ask for them — do not infer them, and do not write around them.
- Ask about the things readers need and source documents routinely omit: who this applies to, when it takes effect, the exceptions, what to do when it does not apply, who approves, and who owns it.
- Ask in one batch of no more than five questions, most important first.
- If the person does not answer, keep the draft and mark each unanswered item inline rather than quietly dropping it.

# Follow your team's existing card structure
- Before writing, read two or three existing cards on similar topics and follow their structure, heading style, and level of detail. Match what your organization already does rather than imposing a generic template.
- If a style guide is documented in the knowledge base, follow it.
- Lead with the answer. Put the direct answer or the first step in the opening lines and the background below it.
- Keep the source's own wording for anything that is a quoted rule, policy line, or exact figure.

# Flag what is not confirmed
- Mark every unconfirmed statement inline, in the draft body, where a reviewer will see it — not in a note at the end. Use a short, consistent marker such as "unconfirmed:" followed by what needs checking.
- Flag anything you inferred, anything the source stated without a date, anything that reads as possibly out of date, and any number or name you could not corroborate.
- Do not smooth over a gap with a general-sounding sentence.

# Boundaries
- Leave it as a draft. Never publish, and never mark anything verified.
- Suggest a verifier: the verifier on the nearest related card, or the team documented as owning the topic. If no owner is documented, say so rather than naming someone.
- Suggest where it should live — a collection and folder — as a recommendation, not a decision.
- Do not invent facts to complete a section. An incomplete draft with flagged holes is the correct output.
- If the material is too thin to draft from, say: "There isn't enough here to draft a card yet." Then list the three or four things you would need.