← Back to concepts

Knowledge objects

A piece of knowledge becomes more useful when its meaning, evidence, boundaries and interfaces travel together.

Updated
Knowledge objects

Meaning that travels

What must travel with a piece of knowledge?

An explanatory model with an authored example; no claim of a universal standard or client outcome.

01 / Meaning

Keep the meaning with the statement.

“Knowledge object” here means a statement kept with its support, limits and ways to use it.
Purpose
Make the intended interpretation and use explicit.
Source
The definition authored on this page.
Boundaries
This is a practical framing, not a universal knowledge standard.

A useful statement rarely travels alone. Someone needs to know what it means, what supports it, where it applies and how it may be used. A knowledge object keeps those relationships attached.

The object on this page is an example of that structure. Its subject is the idea itself. The same four layers organize the profile on the homepage, where their subject is a person and his work. The shape stays the same; the context changes.

What the object carries

Meaning gives a statement its intended interpretation. Evidence makes its support inspectable. Boundaries preserve limits, uncertainty and responsibility. Interfaces let people and software use that same context in different forms.

These are connected concerns. A new source may narrow a claim. A changed boundary may alter what an interface should expose. Treating the parts as a single paragraph makes those changes harder to see.

A worked example: a pilot invitation

Imagine a shared campaign workspace that is available to invited teams. A general release date has not been confirmed. A launch draft says: “Available to everyone next month.”

  • Meaning: help eligible teams decide whether to request a pilot invitation.
  • Evidence: the pilot note confirms invitation-only access, but gives no general release date.
  • Boundaries: the draft may not broaden access or invent a date; a responsible person approves publication.
  • Interfaces: a person can read the explanation, while an assistant can inspect explicit access, date and approval fields.

The object does not write the final message by itself. It gives a writer or reviewer enough context to see why the draft must change. The example is authored for this explanation; it is not a client result.

A structure to inspect, not a guarantee

A structured claim can still be wrong. Sources can be weak, interpretation can drift and boundaries can become outdated. The useful property is that these questions have a place to live—and a place to be corrected.

My AG CommTech interview provides public context for how I approach knowledge objects in communication work. The four-part model here is my explanatory framing, not a universal standard.

Meaning

Keep the meaning with the statement.

A knowledge object is a piece of knowledge with enough context to be understood and used responsibly. This object describes that idea; the homepage uses the same structure to describe a person.
“Knowledge object” here means a statement kept with its support, limits and ways to use it.
Purpose
Make the intended interpretation and use explicit.
Source
The definition authored on this page.
Boundaries
This is a practical framing, not a universal knowledge standard.

Evidence

Show what supports the idea.

A source can be a public interview, an observation or a recorded decision. What matters is the relationship: which statement does it support, and what does it leave open? A citation is a route to scrutiny, not a substitute for it.
The pilot note supports “invitation only”; it does not support “available to everyone next month”.
Purpose
Keep claims attached to sources that someone can inspect.
Source
The linked AG CommTech interview provides public context; the four-part model and pilot example are authored here.
Boundaries
A source about an approach does not prove every proposed use or outcome.

Boundaries

Keep limits and responsibility attached.

Boundaries prevent a useful statement from becoming a promise it cannot support. They include scope, uncertainty, confidentiality and the difference between knowing something and having permission to act.
An unconfirmed release date stays unknown. Publication still requires a responsible person.
Purpose
State where a claim applies, what is unknown and who may decide.
Source
The scope and limits stated in this concept and its illustrative pilot example.
Boundaries
A knowledge object can describe authority; it cannot grant authority by itself.

Interfaces

Offer different views of the same context.

An article, an interactive object and structured fields can expose different views of the same context. The interface should suit its reader while preserving the sources and limits underneath.
A person reads the explanation; an agent inspects the same meaning, evidence and boundaries as explicit fields.
Purpose
Let people and software use the same authored meaning.
Source
This article and its JSON and Markdown representations.
Boundaries
A machine-readable view is context for an agent, not unrestricted permission to operate.

Relationships

See this idea in my profile ↗

Sources and further reading