Context is operating structure
A folder of documents is not context. A working layer distinguishes the company, the customer, the rule, the example, the historical event, and the current state.
That structure lets the same knowledge support several workflows without one giant prompt becoming the system.
Source hierarchy matters
Two documents can both be authentic and still disagree. The system needs a rule for which source wins, when freshness matters, and when a person must decide.
Without a source hierarchy, retrieval makes contradictions faster to find but not safer to use.
Load only what the workflow needs
More context is not always better. Excess context increases cost, latency, leakage risk, and instruction collision.
The useful unit is the smallest approved context package that supports the current action.
What it cannot do
It cannot repair missing company decisions, approve itself, or establish truth from unowned records.
The context layer makes operating knowledge usable. The company still has to own the knowledge.