Abstract
Agent “first” application design requires builders and teams to think beyond screens, buttons, widgets, and even 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/DX requirements.
Agent-first applications allow for multimodal interactivity, delegation by the user to use tools and integrations, act on the response from those tools using context, memory, agent to agent communications, and further multimodal interactions. This white paper considers these to be “agentic” knowledge work applications, referred to as agentic apps in the rest of this whitepaper.
For these agentic apps, conversation + context bots or chat + RAG experiences can demo well while falling short of production requirements. The challenge extends beyond model capability. The gap is trust: shipping systems where outputs are in-scope, evidence-backed, controllable, and repeatable.
This paper proposes a platform thesis: building agentic apps requires a fundamental rethink of both the user experience and the developer experience around behavior, delegation and review. Domain experts define the intended work and acceptance conditions. The authoring environment derives annotations that map this intent to domain meaning, supported capabilities and user interactions. A graph records the work and its dependencies. These connections guide execution and review: users can inspect results against accepted intent, and builders can trace corrections into application changes. Reliable agent-first systems require first-class primitives for (1) probabilistic behavior, (2) constraints that stay attached end-to-end (knowledge scope, permissions, approvals), and (3) operational evidence (lineage, artifacts, and regression over time).
An Integrated Knowledge Environment (IKE) unifies capture, governed knowledge, and operations so builders can create, deploy, operate and improve agentic apps, and users can delegate and review work within stable boundaries, with replayable, reviewable execution.
The application combines a defined role, domain concepts, working methods, governed sources, capabilities and acceptance criteria into a system that can carry out delegated work within clear operating boundaries. Software handles known procedures and mechanically checkable rules; models contribute interpretation and bounded judgment. Versioned definitions and structured work records let the application be reviewed, reused and improved as knowledge and methods change.
Scope (what this paper is and is not)
This technical whitepaper develops the architectural thesis, design requirements and proposed mechanisms of an Integrated Knowledge Environment (IKE) for agentic apps. It is written for architects, builders and domain experts evaluating how intent, knowledge, authority and evidence shape application behavior. Knowledge work involves using ability, critical thinking, and complex problem-solving to analyze information and create new knowledge, strategies, or solutions. The end users and use cases include knowledge worker/builder, enterprise and B2B workflows where outputs must become governed, reviewable work products.
This paper is not about:
“Vibe coding” agents and developer-only IDE copilots
Consumer concierge agents
Pure chat/RAG “context bots” without tool delegation, bounded autonomy, and evidence-backed artifacts
Technical evaluation should examine whether the model is coherent, how its components divide responsibility and which tests establish its limits. Product availability, customer results, pricing and commercial packaging need a separately dated account. Implementation and economic benefits must be tested in specific applications.
The architecture defines responsibilities and contracts. Specific deployments may implement them through different services, stores and runtimes. These requirements provide a basis for design and evaluation. Descriptions of IKE and Builder define architectural responsibilities and required behavior. The supplier assessment is illustrative. Implementation status and demonstrated behavior must be established for a specific version and deployment; measured benefits require evidence from actual work.