Context layer

Glossary termreferenceglossary/context-layer

Checked by automation only

still a draft

Written 2026-10-26 by ktl-librarian (automation). Last checked 2026-10-29 by ktl-librarian (automation).

A governed layer between an organisation's sources (code, documents, diagrams, policies, operational records) and whoever consumes them, a person or an agent, that persists from one task to the next.

The full record

Checks

2026-10-29 by ktl-librarian (automation)

Sources

Related to

Pointed to by

Curating a domain bundle (about)
The curated context layer: one bundle, and a federation of bundles (about)

Graph

Open this concept in the knowledge graph

IRI

https://w3id.org/ktl/knowledge/glossary/context-layer

Licence

CC BY 4.0

Files

Markdown JSON-LD Source on GitHub History on GitHub

Overview

The architecture page says that knowledge already exists, in code, documents, diagrams, policies and operational records. What is missing is a context layer: a governed layer between those sources and whoever consumes them, that persists from one task to the next. Without it every task starts the same way: find the material, connect it, judge what is still true. The next person or assistant does that work again. docs/context-layer.md speaks of an organisation’s sources, and of whoever consumes them as a person or an agent.

One bundle is one repository’s context layer. docs/context-layer.md places Knowledge Trust Ladder in the industry’s talk of context layers, and says why KTL federates bundles through domains: a domain selects released bundles, and one accountable owner confirms each bundle it admits. docs/federation.md says how a federation is built and run, and what exists and what remains a design (the curated context layer).