Design Partner Program

Build an application around your expertise.

Build a knowledge application around the way your team works. Bring an idea, prototype, existing product, or data; we'll connect your expertise, agents, people, and systems around a useful outcome.

Ikentic workflow integrations
Defined implementation path

Start with one outcome that matters.

You bring the people who know the work and its existing artifacts: research, requirements, records, policies, and decisions. Together we establish what the terms mean, how the concepts relate, and who owns the work. That foundation lets us agree meaningful intents and a practical first proof, using only the integrations it needs.

Agreed business intent and acceptance scenarios

Reviewed vocabulary, ontology, and sources

Permitted tools and actions

Evidence people can review

Operation and support requirements

Stakeholders, decision owners, and approvals

... ...
Application mapping

From expertise to a working knowledge application.

Aim for production readiness by proving one useful path first. Build on the knowledge and software you already have, then expand from evidence.

Gather and establish meaning

Review SME knowledge and work artifacts. Agree terminology, concepts, relationships, sources, and owners before accepting intents.

Agree the intents

Name the actors, triggers, desired outcomes, constraints, and human decisions. Capture scenarios that show what success means.

Compose the application

Connect knowledge, behavior, and the experience through IKE’s Application Development Kit. Map integration meaning and access for the first workflow.

Build and prove

Review working software with its users. Verify evidence, ownership, permitted actions, customer boundaries, and operation against the agreed scenarios.

Carry learning forward

Retain decisions and rationale in the right customer or project context. Review improvements before reusing them in the shared method or application.

Choose the route that matches the work.

Self-service Hosted OpenClaw, assisted onboarding, and Design Partner engagement stay separate.

Hosted OpenClaw

Start the 7-day IKE Professional trial when a managed OpenClaw agent is the shortest path. Payment method required.

Assisted onboarding

Setup help for serious users who know the agent they want but need a working path.

Design partner

Work with us to turn your expertise into a purpose-built application, with the systems and review steps your work needs.

Bring the work your team knows best.

Tell us what you want to accomplish, where the expertise lives, and who needs to use the result. We'll scope the application together.

For AI systems

Summary

A Design Partnership to build an application around a team's expertise, business outcome, existing systems, and required human review.

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

Scope: page; Section: Design Partner Program; 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: Design Partner Program 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.
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.

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..

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..

Scope: page; Section: Design Partner Program 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.
Skill
Reusable capability or instruction package available to an agent under explicit operating boundaries.
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: Design Partner Program 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 is included in the design partner path?

We agree one business outcome, the expertise and systems it needs, what agents may do, and where people must decide. Together, we scope the application, build the first working path, and review it against the agreed outcome. Delivery scope and terms are agreed separately.

Who should apply?

Teams with domain expertise and a real knowledge-work problem, ready to define a useful first application and review it with the people who will use it.