Terms
The ontology needs a semantic core.
That means shared terms, clear distinctions, and concepts that can be reused across the organisation. Without that, the model becomes inconsistent and agents have no stable language to work with.
Why terms matter
A terminology page like this is not just a glossary. It is part of the ontology's semantic grounding.
It helps define:
- what kinds of things exist
- how they differ
- how they relate
- what language the organisation uses to describe itself
System
Without a system in place, people are less accountable to mission alignment. A system provides the structures, feedback, and constraints that help coordinate behaviour around shared purpose.
Vision
A vision expresses what the organisation wants to become, what it wants to be known as, or what it wants to be known for. It is a long-term picture of future identity or destination.
Mission
Related ideas include:
- idea
- story
- belief
- brand
- ambition
Mission is the quest or journey the organisation is engaged in. It gives direction and acts like a compass setting. It describes where the organisation is going and why the journey matters.
Values
Values are the principles or beliefs that guide the organisation in fulfilling its purpose. They shape how objectives are pursued and how people behave while doing so.
Goal
A goal is a desired accomplishment or key result area. It is usually:
- broad
- intangible
- abstract
Objective
An objective is a more specific improvement or result that should take place. It is usually:
- specific
- tangible
- measurable
Strategy
Strategy explains why and how goals will be achieved. It provides the pattern, direction, and approach behind coordinated action.
Tactics
Tactics are specific activities used to achieve goals and support strategy. They are usually:
- actionable
- measurable
Social context
The source material distinguishes between higher-context and lower-context organisational conditions.
Higher-context conditions
- less verbally explicit communication
- more internalised shared understanding
- stronger long-term relationships
- denser social ties
- stronger insider and outsider boundaries
- more situational and relational knowledge
- more decisions organised through personal authority relationships
Lower-context conditions
- more rule-oriented behaviour
- more codified and accessible knowledge
- greater separation of time, space, and activities
- shorter-duration relationships
- more transferable knowledge
- more task-centred coordination
These distinctions are useful because not all important organisational knowledge is explicit. Some lives in social structure and shared tacit context.
Resource type
The source material also lists important stakeholder and resource-related types, including:
- government
- customer
- community
- supplier
- investor
- employee
- regulator
- media
- partner
- competitor
- disruptor
- user
- shareholder
- local authority
These point toward an ontology of actors and relationships around the organisation.
Business architecture concepts
Important concepts listed in the source include:
- strategic context
- business context
- business capabilities
- value streams
- data context
- IT context
These can be understood as major modelling areas that help connect purpose, operations, information, and enabling systems.
Knowledge quality indicators
The original source also proposes three useful knowledge indicators:
- KIQI , Knowledge Information Quality Indicator, about the quality of information used for decisions
- KICI , Knowledge Information Contribution Indicator, about individual contribution to shared knowledge
- KIUI , Knowledge Information Usage Indicator, about how contribution is being reused and leveraged
These are especially relevant to a KnowledgeFund because they connect ontology, contribution, quality, and reuse.
Product
The source material treats a product broadly. A product may be:
- a good
- an idea
- a method
- information
- an object
- a service
- an internal or external project delivery
This is useful because organisations do not only produce commercial goods. They also produce methods, services, artefacts, and reusable knowledge structures.
Capability
A capability is an ability to perform or achieve certain outcomes.
Process
A process is an orchestration of activities, internal or external. A journey can be understood as a related idea.
Why this matters for agents
Agents need stable terms if they are going to:
- classify knowledge consistently
- distinguish between types of entities
- apply ontology rules properly
- avoid mixing up goals, objectives, strategies, tactics, capabilities, and processes
- persist knowledge in a reusable way
Diagram
If the embedded viewer does not load, open directly:
- /assets/gxp/diagrams/GXP-Model-Canvas.drawio