Build around a Persona and the knowledge it uses. Add the screens, integrations, and review steps your team needs, with your systems retaining their records and rules.
Start with a scoping conversation. We agree the first working slice and current Design Partnership terms together.
Start from a workflow idea or a Persona you already use. Its role, instructions, and chosen Knowledge Collections provide working context. Your application adds the screens, integrations, and review steps around it. Together, we shape the application around the decisions people need to make.
Leave the first conversation with a clearer scope: the task, the connections, and what success should look like.
Who does the work? What result should they be able to inspect and use? Start with a briefing, a review, or another specific knowledge task.
Bring the documents, APIs, and product screens the task touches. Your existing systems keep ownership of their records and rules.
Name what the agent may do and where a person must review or approve the next step. Agree the evidence that will make the first slice useful.
Omni Arcs Product Studio built and operates Hosted OpenClaw with IKE. It brings a full agent framework, dedicated hosting, Personas, knowledge, authentication, and shared access into one managed application.
Your application can be shaped around a different job. Builders add the interface, workflow, code, and integrations while IKE keeps the agent's working context connected. Application code handles permission checks, API calls, rendering, and navigation; models handle interpretation where needed.
Availability, ownership, and what to bring.
The IKE ADK is in private preview. Discuss your workflow with the team to establish the current access path and extension scope. Purpose-built applications are delivered through Design Partnerships.
Your source systems retain ownership of records, policies, and valid actions. The application connects permitted knowledge and tools to its Persona and workflow. Integration and access boundaries are part of scoping.
Bring one user role, one task, the systems and source material it touches, and the result people need to review. Include the actions that require permission or human approval.
Professional supplies the managed Smart Agent path. Design Partnership delivery, integration scope, fees, and terms are agreed separately with the team.
Start with the role, source systems, and result your team needs. We'll discuss the current Design Partnership and preview access path.
Extend a Persona and its knowledge into an Agent Application with your own screens and integrations. Design Partnerships available; IKE ADK in private preview.
Site-wide definitions, relationships, and availability: /llms.txt.
Agent application (ike.product.agent_application) — An Agent Application is the user-facing AI application for a knowledge-work use case. It can combine zero or more Persona Bindings with capabilities and deployment intent. It may use Direct Agent for a conversation, Smart Agent for a managed framework, or a purpose-built interface 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..
Skill (ike.entity.skill) — Reusable capability or instruction package available to an agent under explicit operating boundaries..
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..
The IKE ADK is in private preview. Discuss your workflow with the team to establish the current access path and extension scope. Purpose-built applications are delivered through Design Partnerships.
Your source systems retain ownership of records, policies, and valid actions. The application connects permitted knowledge and tools to its Persona and workflow. Integration and access boundaries are part of scoping.
Bring one user role, one task, the systems and source material it touches, and the result people need to review. Include the actions that require permission or human approval.
Professional supplies the managed Smart Agent path. Design Partnership delivery, integration scope, fees, and terms are agreed separately with the team.