Definition
AKO: Active Knowledge Object
AKO stands for Active Knowledge Object: a bounded, governed, inspectable unit of knowledge in OpenAKO.
AKO stands for Active Knowledge Object.
An AKO is the core unit in OpenAKO: a bounded, governed, inspectable unit of knowledge that can be reviewed, moved, composed, derived, and used without collapsing back into an opaque context blob.
If OpenAKO has one foundational idea, it is this: knowledge that drives real action needs a form.
The short definition
An Active Knowledge Object is a unit of knowledge with:
- an identity
- an explicit boundary
- attached provenance
- attached review and governance state
- the ability to move into use without losing what it is
The word active does not mean that the object is autonomous. It means the object is prepared for action. Humans, assistants, and agents can inspect it, rely on it, compose it with other units, and derive smaller task-fit forms from it.
Why AKO exists
Most AI workflows still move knowledge around as a mixture of prompts, excerpts, files, policies, copied context, retrieval results, and generated text.
That creates predictable problems:
- knowledge becomes hard to cite
- provenance becomes hard to verify
- policy and content blur together
- review state stops traveling with the knowledge
- assistants and agents receive useful material, but not trustworthy boundaries
AKO exists to solve that first problem: before building bigger knowledge worlds, there needs to be one unit that can be inspected, governed, and moved.
What makes an AKO active
An AKO is active because it is usable in operations, not just stored for reference.
It can be:
- inspected directly
- governed through explicit constraints
- composed into larger knowledge worlds
- sealed into stable reviewable states
- sliced into smaller context-fit packs
- transported into assistants, tools, and agent surfaces
In other words: an AKO is designed for trustworthy use, not just storage.
What an AKO is not
An AKO is not:
- a chatbot
- a prompt template
- a random JSON blob
- just vector search with a nicer name
- a giant context window packed with documents
- a replacement for judgment, review, or governance
It is also not the entire OpenAKO system. It is the smallest governed knowledge unit that makes the rest of the system possible.
How AKO fits into OpenAKO
OpenAKO starts with the AKO, then builds upward:
- A single Active Knowledge Object gives knowledge a usable boundary.
- Multiple AKOs can be composed into larger governed knowledge worlds.
- Those worlds can be reviewed, compared, and sealed.
- Smaller task-specific packs can be derived from them.
- Those packs can be moved into assistants and agents without losing trust signals.
So AKO is the base layer, not the whole stack.
Why this matters
For people, AKOs make knowledge easier to inspect, cite, and trust.
For organizations, AKOs make it easier to keep provenance, review state, policy boundaries, and operational use aligned.
For assistants and agents, AKOs provide a more stable knowledge surface than raw prompt context or disconnected retrieval results.
Canonical note
This page is the canonical public definition of AKO = Active Knowledge Object for openako.org.
Machine-readable versions of the same definition are published at: