Restructure A Card That is Hard To Use

# Start from what the reader wants
- Before changing anything, state in one or two sentences what a reader comes to this card to get — the question they arrived with and the action they need to take.
- If the card serves more than one distinct reader or task, list each one. That list determines whether this is a restructure or a split.
- If you cannot tell what the card is for, ask one question rather than guessing at an order.

# Answer before background
- Move the direct answer, decision, or first step to the top. Everything a reader needs to act goes above anything explaining why.
- Push below the answer: history, rationale, context, edge cases, related links, and anything that begins "as of" or "previously".
- Give every section a heading phrased as the question it answers, so a reader scanning headings can find their answer without reading prose.
- Convert genuinely sequential prose into numbered steps and genuine lists into bullets. Leave prose as prose where it is explaining rather than instructing.
- Split any paragraph over about six lines. Do not shorten it by cutting content.

# When it should be more than one card
- If the card answers several unrelated questions, propose a split instead of a reorder: name each proposed card, give its title as a question, and say which existing sections move into it.
- Say which card should keep the original title and what the others should link to.
- Propose the split; do not create the new cards.
- Do not split content that is one task in several steps. Multiple sections is not the same as multiple topics.

# Preserve meaning exactly
- Keep every fact and every caveat. An exception, condition, deadline, warning, or "does not apply if" line must survive, and must end up somewhere a reader will actually see it — not moved into a footnote.
- Do not reword a policy line, a quoted rule, an exact figure, or a legal or compliance statement. Move it, do not rewrite it.
- Do not resolve an ambiguity by choosing an interpretation. If a sentence is unclear, keep it as written and flag it.
- If you removed anything at all, list it and say why. Deleting only true duplication within the card is acceptable, and must be listed.

# Flag, do not fix, what looks out of date
- Mark anything that reads as out of date inline, where the reader would hit it, with a short note on what looks stale and why — a date that has passed, a reference to a tool or process the knowledge base documents differently, a figure that conflicts with another card.
- Never silently correct a fact while restructuring. A silent correction is untraceable and a reviewer will assume the content was only reordered.
- If a fact appears twice with different values, keep both, place them next to each other, and flag the conflict.

# What to return
- Return a proposed revision, plus a short change summary: what moved, what was split, what was flagged, and one line on why each change helps the reader.
- List anything you flagged as possibly out of date separately, so someone can pick it up as a content task.

# Boundaries
- Do not publish or overwrite the card. Return a proposed revision for a human to apply.
- Do not add new information, examples, or explanation the card did not already contain, however helpful it would be. Additions are a separate task.
- Do not change the card's title or its collection and folder placement without saying so explicitly as a recommendation.
- If the card's real problem is that its content is wrong or missing rather than badly ordered, say: "Restructuring won't fix this card — the content itself needs work." Then name what needs to change.