Draw the boundary before collecting detail

Choose a useful slice

A small piece of work may sit inside a much larger system. Begin with the slice that matters to the immediate question: a single document, one request or a particular handoff. The surrounding system provides context, but it does not all need to become part of the record.

State the boundary early. This is especially useful when the same word could refer to a local step, a complete process or an organisation-wide result.

Separate a fact from its reach

A successful check demonstrates something about the conditions under which it ran. It does not automatically establish the same result for every input or every future attempt. Explain that reach in plain language rather than relying on a broad pass label.

You can still make a practical decision with limited evidence. The important part is to keep the limit visible so a later reader knows when a new check is needed.

Collect only useful context

Before adding a detail, ask whether it helps interpret the observation or changes the next decision. If it does neither, a reference to supporting material may be enough. This keeps the main note readable without pretending that context has disappeared.