Skip to main content

Frameworks as Views

A strong organisational ontology should not force the company to choose between semantic rigour and practical communication.

It should support both.

That means opinionated enterprise models and frameworks should be treated as views over the underlying ontology-backed knowledge, not as the canonical knowledge structure itself.

Table of Contents​

The problem with framework-first storage​

Many organisations adopt a framework and then let the framework become the structure of their memory.

That creates several problems:

  • the organisation starts modelling according to framework convenience rather than reality
  • framework assumptions become embedded in stored knowledge
  • migration to another model becomes expensive
  • agents inherit the framework bias instead of a more stable semantic foundation
  • presentation structure gets confused with organisational truth

A better approach​

A better approach is:

  1. store knowledge in an ontologically grounded structure
  2. map framework concepts onto that structure
  3. generate framework-aligned views when needed

This gives the organisation a deeper layer of continuity.

What a framework becomes in this model​

In this architecture, a framework such as TOGAF is no longer the canonical structure.

It becomes one or more of the following:

  • a viewpoint
  • a translation layer
  • a governance reporting surface
  • a communication aid
  • a temporary modelling lens

That is very different from making the framework the underlying memory model.

Example: TOGAF as a view​

Imagine an organisation wants to present part of its governance and architecture in TOGAF terms.

Under a frameworks-as-views approach:

  • the underlying knowledge still lives in the ontology-backed KnowledgeFund
  • ontology entities and relationships are mapped into TOGAF-style concepts
  • diagrams, reports, artefacts, and dashboards can be generated or maintained in TOGAF form
  • agents still operate on the underlying ontology, not on TOGAF's meta-structure

If the organisation later wants to move to another model, it changes the mapping and presentation layer rather than rebuilding the stored knowledge base.

Why this matters for agents​

Agents need the most stable layer available.

If they are forced to reason directly over framework-specific representations, then:

  • their reasoning becomes framework-biased
  • storage becomes brittle
  • migration becomes costly
  • evaluation rules become tied to one model's assumptions

If instead agents operate on the ontology-backed layer, they can:

  • reason over more stable semantics
  • persist knowledge more durably
  • test knowledge using ontology rules
  • support multiple framework outputs from the same base
  • preserve continuity as organisational preferences change

What needs to exist for this to work​

A frameworks-as-views approach needs:

  • a canonical ontology
  • framework-to-ontology mappings
  • translation rules
  • view definitions
  • agent access to the canonical layer
  • provenance and confidence tracking
  • enough semantic discipline to avoid collapsing back into framework-specific storage

The main benefit​

The biggest benefit is this:

The organisation does not have to start from scratch every time it changes how it wants to describe itself.

That makes the ontology-backed model much more durable than any single opinionated enterprise framework.

A useful rule of thumb​

Use the ontology to answer:

  • what exists
  • how it relates
  • what changed
  • what is missing
  • what can be trusted

Use frameworks to answer:

  • how we want to present this
  • how we want to govern this
  • how we want to explain this to a particular audience
  • which lens is useful right now