Context needs an objective, and only a process has one
Relevance is not a property of context. It is a relation between context and a purpose, and a regulatory process supplies a purpose that outlasts any question.
Context has become the word the market uses for what enterprise AI is missing. It is now a product name in catalogues and semantic layers, entity resolution, process intelligence, risk and compliance tooling, and enterprise architecture. Each supplies context about a different kind of thing. Few connect to the others, so an institution buying context still joins the pieces itself, one obligation at a time.
A bucket of context
Context is only valuable relative to a purpose. The original engineering definition of the term made relevance depend on the user's task. Today's AI tooling makes it depend on the prompt. Both place the purpose in the moment of asking, which works for a person at a screen.
It does not work for a process that runs without a person at the moment of asking. When an agent is running the process, there is no user whose task can supply the relevance. Context that is not held against an objective is a bucket: searchable, ranked by resemblance to the question, and interpreted differently every time.
Three things only a process has
An objective. A dataset does not exist to achieve anything. A regulatory process exists to produce an approved outcome, and that outcome decides which context is relevant, what good looks like and when the answer is wrong.
An order. Input, definition, rule, calculation, check, control, review and output. A catalogue can say a rule exists and who owns it. It cannot say that the rule fires after one transformation and before one control, because order is not a property of a list of assets.
An output that is examined. The return, the risk report, the disclosure. A description of data is never examined. A number is, and every hard question from a supervisor is asked about it.
That is why xflow builds context at the level of the process. The process is where an entity, an obligation and a data value meet, and the only place a purpose can be attached to all three.