{"body":"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.\n\nThe 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.\n\n## What the object carries\n\nMeaning 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.\n\nThese 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.\n\n## A worked example: a pilot invitation\n\nImagine 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.”\n\n- **Meaning:** help eligible teams decide whether to request a pilot invitation.\n- **Evidence:** the pilot note confirms invitation-only access, but gives no general release date.\n- **Boundaries:** the draft may not broaden access or invent a date; a responsible person approves publication.\n- **Interfaces:** a person can read the explanation, while an assistant can inspect explicit access, date and approval fields.\n\nThe 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.\n\n## A structure to inspect, not a guarantee\n\nA 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.\n\nMy [AG CommTech interview](https://agcommtech.de/2026/03/31/weniger-dokumente-mehr-knowledge-objects-wie-zeiss-ki-assistenten-systematisch-aufbaut/) 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.","context_url":"https://www.svenspoede.com/context.json","description":"A piece of knowledge becomes more useful when its meaning, evidence, boundaries and interfaces travel together.","lang":"en","markdown_url":"https://www.svenspoede.com/concepts/knowledge-objects/index.md","objects":[{"body":"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.\n\nThe 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.\n\n## What the object carries\n\nMeaning 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.\n\nThese 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.\n\n## A worked example: a pilot invitation\n\nImagine 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.”\n\n- **Meaning:** help eligible teams decide whether to request a pilot invitation.\n- **Evidence:** the pilot note confirms invitation-only access, but gives no general release date.\n- **Boundaries:** the draft may not broaden access or invent a date; a responsible person approves publication.\n- **Interfaces:** a person can read the explanation, while an assistant can inspect explicit access, date and approval fields.\n\nThe 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.\n\n## A structure to inspect, not a guarantee\n\nA 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.\n\nMy [AG CommTech interview](https://agcommtech.de/2026/03/31/weniger-dokumente-mehr-knowledge-objects-wie-zeiss-ki-assistenten-systematisch-aufbaut/) 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.","boundary":"An explanatory model with an authored example; no claim of a universal standard or client outcome.","id":"knowledge-object","parts":[{"body":"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.","boundary":"This is a practical framing, not a universal knowledge standard.","example":"“Knowledge object” here means a statement kept with its support, limits and ways to use it.","id":"meaning","label":"Meaning","purpose":"Make the intended interpretation and use explicit.","related":["evidence","interfaces"],"source":"The definition authored on this page.","summary":"Make the intended interpretation and use explicit.","title":"Keep the meaning with the statement."},{"body":"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.","boundary":"A source about an approach does not prove every proposed use or outcome.","example":"The pilot note supports “invitation only”; it does not support “available to everyone next month”.","id":"evidence","label":"Evidence","purpose":"Keep claims attached to sources that someone can inspect.","related":["meaning","boundaries"],"source":"The linked AG CommTech interview provides public context; the four-part model and pilot example are authored here.","summary":"Keep claims attached to sources that someone can inspect.","title":"Show what supports the idea."},{"body":"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.","boundary":"A knowledge object can describe authority; it cannot grant authority by itself.","example":"An unconfirmed release date stays unknown. Publication still requires a responsible person.","id":"boundaries","label":"Boundaries","purpose":"State where a claim applies, what is unknown and who may decide.","related":["evidence","interfaces"],"source":"The scope and limits stated in this concept and its illustrative pilot example.","summary":"State where a claim applies, what is unknown and who may decide.","title":"Keep limits and responsibility attached."},{"body":"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.","boundary":"A machine-readable view is context for an agent, not unrestricted permission to operate.","example":"A person reads the explanation; an agent inspects the same meaning, evidence and boundaries as explicit fields.","id":"interfaces","label":"Interfaces","purpose":"Let people and software use the same authored meaning.","related":["meaning","boundaries"],"source":"This article and its JSON and Markdown representations.","summary":"Let people and software use the same authored meaning.","title":"Offer different views of the same context."}],"premise":"What must travel with a piece of knowledge?","relationships":[{"from":"meaning","label":"is supported by","to":"evidence"},{"from":"evidence","label":"sets the limits of","to":"boundaries"},{"from":"boundaries","label":"constrains","to":"interfaces"},{"from":"interfaces","label":"carries into use","to":"meaning"}],"role":"Meaning that travels","scene":"knowledge-object","sources":[{"id":"source-knowledge-objects-zeiss-ai-assistants-commtech-2026","title":"AG CommTech — Less documents, more knowledge objects – How ZEISS builds AI assistants systematically","type":"public-record","url":"https://agcommtech.de/2026/03/31/weniger-dokumente-mehr-knowledge-objects-wie-zeiss-ki-assistenten-systematisch-aufbaut/"}],"summary":"A piece of knowledge becomes more useful when its meaning, evidence, boundaries and interfaces travel together.","title":"Knowledge objects","type":"concept","updated":"2026-09-19","url":"https://www.svenspoede.com/concepts/knowledge-objects/"}],"plain":"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.\nThe 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.\nWhat 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.\nThese 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.\nA 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.”\nMeaning: 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.\nA 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.\nMy 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.","template":"concept","title":"Knowledge objects","url":"https://www.svenspoede.com/concepts/knowledge-objects/"}