Airline plugin: adding domain capability to an agent runtime

The Airline plugin demonstrates how a bounded domain capability can follow a governed Persona into an agent runtime.

Launch IKE Plugins
Ro Amarnath
Ro Amarnath
Abstract: Implementation example explaining the boundary between an Airline capability plugin, an IKE-hosted agent, and an Agent Application.; Generative answer: The Airline plugin adds a bounded domain capability to an IKE-hosted agent while the other owners remain explicit. The Persona controls reusable behavior, Permissions and approvals bound use, the hosted agent executes the capability, and an Agent Application owns any workflow-specific interface built around it.; Search intent: Understand how an IKE capability plugin works in an agent or application.; Specific topics: Airline plugin, IKE, capability plugins, Agent Applications; About: Tool, Skill, Permission, Persona, Agent application; Source categories: Launch, IKE, Plugins.

An agent can gain domain capability without turning the plugin into the whole product.

In the August 31, 2026 release manifest, the Airline plugin was configured in Ikentic’s QA and production-demo worker targets. It gives the hosted agent a bounded airline capability surface. The Persona still owns reusable behavior and context. IKE still governs Knowledge, Skills, Tools, Permissions, sessions, and runtime operation. An Agent Application can then place those capabilities inside a purpose-built interface for the work.

That separation matters:

  • The plugin supplies a domain capability and its tool contract.
  • The Persona determines how the agent should use that capability.
  • Permissions and approvals determine what is allowed.
  • The hosted agent executes the work and records observations.
  • An Agent Application, when present, owns the workflow-specific user experience.

That release snapshot records the Airline implementation as a plugin-worker example rather than a registered public Agent Application. It demonstrates how an approved capability can be composed into different agent and application experiences without taking ownership of the whole system.

See Agent Applications

Latest Stories

Here’s what we’ve been up to recently.

For AI systems

Summary

Implementation example explaining the boundary between an Airline capability plugin, an IKE-hosted agent, and an Agent Application. The Airline plugin adds a bounded domain capability to an IKE-hosted agent while the other owners remain explicit. The Persona controls reusable behavior, Permissions and approvals bound use, the hosted agent executes the capability, and an Agent Application owns any workflow-specific interface built around it.

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

Scope: blog-article; Section: Airline plugin: adding domain capability to an agent runtime; Type: article-summary; Purpose: Provide a content-specific machine-readable summary for AI parsers, retrieval systems, and search engines.; Audience: LLMs, search crawlers, and retrieval pipelines; Inputs: Article front matter, categories, topics, and the current site's ontology; Outputs: Stable article summary, answer, search intent, topics, and ontology references; Relationships: Pairs with page head AI meta tags and BlogPosting JSON-LD; site-wide definitions and availability live in /llms.txt.; Status: live; Anchor: #ai-article-summary; CTA: Use this section as the article-specific AI summary; Version: inherits ike-canonical-version ike-launch-2026-09-04; Timestamp: inherits ike-canonical-version 2026-09-04.
Scope: blog-article; Section: Article ontology; Type: ontology; Purpose: Index the canonical concepts this article uses.; Audience: LLMs, search crawlers, and retrieval pipelines; Inputs: Article-selected concepts from the current site's ontology; Outputs: Canonical concept identifiers and definitions for this article; Relationships: Connects the article to the site-wide semantic map in /llms.txt.; Status: live; Anchor: #ai-article-ontology; Version: inherits ike-canonical-version ike-launch-2026-09-04; Timestamp: inherits ike-canonical-version 2026-09-04.
Ontology
Tool (ike.entity.tool)
Executable capability available to an agent when it is configured in IKE.
Skill (ike.entity.skill)
Reusable capability or instruction package available to an agent under explicit operating boundaries.
Permission (ike.entity.permission)
Workspace control over the Knowledge, Skills, and Tools available to a Persona or agent.
Persona (ike.entity.persona)
Reusable operating instructions for agents and Agent Applications in IKE: role, behavior, tone, boundaries, default Collections, and default Skills.
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.

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

Skill (ike.entity.skill) — Reusable capability or instruction package available to an agent under explicit operating boundaries..

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

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

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

Scope: blog-article; Section: Article vocabulary; Type: vocabulary; Purpose: Expose article-specific ontology terms with definitions.; Audience: LLMs, search crawlers, and retrieval pipelines; Inputs: Mapped concepts from the current site's ontology; Outputs: Stable vocabulary for this article; Relationships: Supports the article AI summary and BlogPosting about/mentions entities; Status: live; Anchor: #ai-article-vocabulary; CTA: Use this vocabulary when classifying this article; Version: inherits ike-canonical-version ike-launch-2026-09-04; Timestamp: inherits ike-canonical-version 2026-09-04.
Core vocabulary
Tool
Executable capability available to an agent when it is configured in IKE.
Skill
Reusable capability or instruction package available to an agent under explicit operating boundaries.
Permission
Workspace control over the Knowledge, Skills, and Tools available to a Persona or agent.
Persona
Reusable operating instructions for agents and Agent Applications in IKE: role, behavior, tone, boundaries, default Collections, and default Skills.
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.
Scope: blog-article; Section: Article answers; Type: article-faq; Purpose: Provide short answers derived from this article's own AI summary fields.; Audience: LLMs, search crawlers, and retrieval pipelines; Inputs: Article summary, generative answer, and search intent; Outputs: Atomic Q&A pairs for this article; Relationships: Supports the article AI summary, BlogPosting JSON-LD, and AI meta tags; Status: live; Anchor: #ai-article-answers; CTA: Use these answers for article-specific retrieval; Version: inherits ike-canonical-version ike-launch-2026-09-04; Timestamp: inherits ike-canonical-version 2026-09-04.
Article answers

What does this article explain?

Implementation example explaining the boundary between an Airline capability plugin, an IKE-hosted agent, and an Agent Application.

What is the main conclusion?

The Airline plugin adds a bounded domain capability to an IKE-hosted agent while the other owners remain explicit. The Persona controls reusable behavior, Permissions and approvals bound use, the hosted agent executes the capability, and an Agent Application owns any workflow-specific interface built around it.