Context — What Must It Have In Front Of It?

A test, rather than a template:

Could a competent stranger load this and act correctly, without asking you anything?

If the honest answer is "they would need to check with me on a few things" — those few things are the context package's real content. Everything else is already obvious enough not to need writing.

Three properties distinguish a working package from a document nobody reads:

• Reloaded, not remembered. Present at the start of every cycle, not handed over once.
• Evidenced, not asserted. Rules that carry their reason are followed; rules that arrive as commands are worked around.
• Dated. Anything that can go stale says when it was last checked.

A caution before you build one

The examples in this module come from an operation where context must be total, because the workers have no memory at all. A human team is never in that position. Colleagues carry undocumented shared understanding that does real work, and writing all of it down would be waste.

So the question worth holding as you build: which parts of your package would be unnecessary for a human colleague — and what does that tell you about where the boundary actually sits?

The test: could a competent stranger load this and act correctly, without asking you anything?