GUIDE · ORGANIZATIONAL CONTEXT
How to build context people and agents can use.
An Understanding Layer starts with a simple question: what do the data mean within the organization? This guide turns that question into a model that process, systems and security teams can review together.
Define entities in a shared language
A customer, asset or event may appear in several systems under different identifiers. Begin with an agreed entity definition and an authoritative source for each attribute. Focus on one workflow where missing context already delays a decision or action, rather than modeling the whole organization at once.
Add relationships that affect a decision
An asset list does not explain ownership or which activity a failure affects. Add relationships such as located at, maintained by or dependent on. Each relationship should support a practical question and be verifiable against people and information the organization recognizes and trusts.
Example: an asset incident
In an illustrative example, an equipment fault is reported. The context model connects the equipment to its site, maintenance owner and an existing work order. That helps determine whether to create a new task or add information to ongoing work. The decision still follows agreed rules and permissions.
Separate source, meaning and action
Source systems hold records. The Understanding Layer defines meaning and relationships. An agent can use that context to answer or propose an action, while controls determine what may execute. This separation helps locate a problem in data quality, a disputed definition or a missing permission.
Check freshness and conflicts
Organizational context changes as people move roles, assets move sites and systems change. Define who updates the model and how conflicting sources are handled. A fluent answer is insufficient when it depends on an outdated relationship or a value without an identifiable source.
What the first map should include
A useful first map contains a business question, a limited entity set, necessary relationships and authoritative sources. Add an accountable owner and the intended decision or action. Review real examples and exceptions with process staff before deciding which part an agent should use.
THE NEXT STEP
Which question needs more organizational context?
Choose one workflow and identify the entities and relationships needed to understand it.