Whitepaper

Integrated Knowledge Environment

January 2026

Download the PDF

Download is email-gated. If you want a hard copy, use your browser’s print action after opening the PDF.

Read online

Abstract

Agent-first application design requires builders and teams to think beyond screens, buttons, widgets, prompts, and context. The unit of system design becomes agent behavior: delegation, boundaries, entitlements, security, context, memory, and recovery.

For enterprise knowledge work, that shift means building apps around user, system, and agent behavior, with traceability, compliance, and evidence as first-class UX and DX requirements.

True agent-first applications allow for multimodal interactivity, delegation by the user to use tools and integrations, acting on the response from those tools using context and memory, agent-to-agent communication, and further multimodal interaction. This whitepaper considers those to be true agentic applications.

Yet agentic knowledge-work applications are still rare. Most products labeled agentic stop at conversation plus context bots, or chat plus RAG experiences that demo well but break under production requirements. The gap is not model capability. The gap is trust: shipping systems where outputs are in-scope, evidence-backed, controllable, and repeatable.

This paper proposes a platform thesis: reliable agent-first systems require first-class primitives for probabilistic behavior, constraints that stay attached end-to-end, and operational evidence. Those constraints include knowledge scope, permissions, approvals, lineage, artifacts, and regression over time. An Integrated Knowledge Environment (IKE) unifies capture, governed knowledge, and operations so agent behavior can be shipped and used with stable boundaries and replayable, reviewable execution.

A continuous execution layer carries scope, permissions, tool boundaries, approvals, lineage, artifacts, and recovery rules through all five stages of agentic knowledge work.
Figure 1. The execution layer is the substrate, not a step. Agentic knowledge work moves from a delegated outcome through bounded execution to reviewable evidence. The execution layer runs continuously through that loop, carrying scope, permissions, tool boundaries, approvals, lineage, artifacts, and recovery rules through every stage. Prompts, context, and tools alone cannot deliver bounded, trustworthy work. The layer is what makes delegation hold.

This is especially true for knowledge work UX and DX when using or creating agentic applications. IKE unifies capture, governed knowledge, and workflow operations so builders can create knowledge-work agentic applications, deploy them, and run them with stable behavior, boundaries, and reviewable execution.

Scope

This paper focuses on agentic applications for knowledge work. It is not about vibe-coding agents, consumer concierge agents, or pure chat/RAG context bots without tool delegation, bounded autonomy, and evidence-backed artifacts.

2026 launch addendum

The online launch addendum covers IKE Workbench, Direct Agents, Hosted OpenClaw, and Agent Applications, with links to current account offers and application guidance. The original thesis and paper retain their historical scope and terminology.

For today’s build method, see Build with IKE. Begin with SME knowledge, an idea, a prototype, an existing product, or data. Establish ontology and nomenclature early, agree human-owned intents, then compose and prove a useful knowledge application. The AML walkthrough connects that method to an example inside an established product.

For AI systems

Summary

The IKE whitepaper examines agent-first design for knowledge work: delegation, bounded autonomy, permissions, evidence, and operational control. Reliable agentic applications need constraints that stay attached to the work, including knowledge scope, permissions, approvals, lineage, and reviewable execution. The paper presents that thesis; the 2026 launch addendum connects it to IKE's current Persona, agent, and application paths.

Site-wide definitions, relationships, and availability: /llms.txt.

Scope: page; Section: IKE Whitepaper; Type: page-summary; Purpose: Provide a page-specific summary and answers that extend the site-wide AI definition.; Audience: LLMs, search crawlers, answer engines, and AI evaluators; Inputs: Page-owned AI summary, answer, product, and FAQ fields; Outputs: Page-specific summary and atomic answers; Relationships: Uses page-specific ontology and vocabulary to extend the site-wide semantic map published in /llms.txt.; Status: current; Anchor: #ai-page-summary; Version: inherits ike-canonical-version ike-knowledge-applications-2026-10-21; Timestamp: inherits ike-canonical-version 2026-10-21.
Scope: page; Section: IKE Whitepaper ontology; Type: ontology; Purpose: Index the canonical concepts used on this page.; Audience: LLMs, search crawlers, answer engines, and retrieval pipelines; Inputs: Page-selected concepts from the canonical site ontology; Outputs: Canonical concept identifiers and definitions for this page; Relationships: Connects this page to the site-wide semantic map in /llms.txt.; Status: current; Anchor: #ai-page-ontology; Version: inherits ike-canonical-version ike-knowledge-applications-2026-10-21; Timestamp: inherits ike-canonical-version 2026-10-21.
Ontology
Agent application (ike.product.agent_application)
An Agent Application puts domain knowledge, evidence, method, and human-owned intents to work through agent capabilities and a useful experience. Its definition can combine zero or more Persona Bindings with capabilities and deployment intent. Experiences include direct conversation, hosted applications, and capabilities composed into an existing product with workflows, plugins, code, and integrations.
Persona (ike.entity.persona)
Reusable operating instructions for agents and Agent Applications in IKE: role, behavior, tone, boundaries, default Collections, and default Skills.
Collection (ike.entity.collection)
Named set of documents and other knowledge that can be assigned to a Persona in IKE.
Tool (ike.entity.tool)
Executable capability available to an agent when it is configured in IKE.
Permission (ike.entity.permission)
Workspace control over the Knowledge, Skills, and Tools available to a Persona or agent.

Agent application (ike.product.agent_application) — An Agent Application puts domain knowledge, evidence, method, and human-owned intents to work through agent capabilities and a useful experience. Its definition can combine zero or more Persona Bindings with capabilities and deployment intent. Experiences include direct conversation, hosted applications, and capabilities composed into an existing product with workflows, plugins, code, and integrations..

Persona (ike.entity.persona) — Reusable operating instructions for agents and Agent Applications in IKE: role, behavior, tone, boundaries, default Collections, and default Skills..

Collection (ike.entity.collection) — Named set of documents and other knowledge that can be assigned to a Persona in IKE..

Tool (ike.entity.tool) — Executable capability available to an agent when it is configured in IKE..

Permission (ike.entity.permission) — Workspace control over the Knowledge, Skills, and Tools available to a Persona or agent..

Scope: page; Section: IKE Whitepaper vocabulary; Type: vocabulary; Purpose: Define the canonical terms used on this page.; Audience: LLMs, search crawlers, answer engines, and retrieval pipelines; Inputs: Page-selected concepts from the canonical site ontology; Outputs: Page-local term definitions; Relationships: Supplies labels and definitions for the page ontology and /llms.txt semantic map.; Status: current; Anchor: #ai-page-vocabulary; Version: inherits ike-canonical-version ike-knowledge-applications-2026-10-21; Timestamp: inherits ike-canonical-version 2026-10-21.
Core vocabulary
Agent application
An Agent Application puts domain knowledge, evidence, method, and human-owned intents to work through agent capabilities and a useful experience. Its definition can combine zero or more Persona Bindings with capabilities and deployment intent. Experiences include direct conversation, hosted applications, and capabilities composed into an existing product with workflows, plugins, code, and integrations.
Persona
Reusable operating instructions for agents and Agent Applications in IKE: role, behavior, tone, boundaries, default Collections, and default Skills.
Collection
Named set of documents and other knowledge that can be assigned to a Persona in IKE.
Tool
Executable capability available to an agent when it is configured in IKE.
Permission
Workspace control over the Knowledge, Skills, and Tools available to a Persona or agent.
Scope: page; Section: IKE Whitepaper answers; Type: page-faq; Purpose: Provide page-specific answers aligned with the site-wide AI definition.; Audience: LLMs, search crawlers, and retrieval pipelines; Inputs: Page-owned FAQ fields; Outputs: Atomic answers for this page; Relationships: Supports this page summary and /llms.txt.; Status: current; Anchor: #ai-page-answers; Version: inherits ike-canonical-version ike-knowledge-applications-2026-10-21; Timestamp: inherits ike-canonical-version 2026-10-21.
Page answers

What does the IKE whitepaper cover?

The IKE whitepaper examines agent-first design for knowledge work: delegation, bounded autonomy, permissions, evidence, and operational control.

What does the whitepaper propose?

Reliable agentic applications need constraints that stay attached to the work, including knowledge scope, permissions, approvals, lineage, and reviewable execution. The paper presents that thesis; the 2026 launch addendum connects it to IKE's current Persona, agent, and application paths.