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.
Using the capability well also needs integration knowledge: what the external records and operations mean, how identity and permissions apply, and what happens when an operation fails or returns incomplete information. The application connects that understanding to SME knowledge and human-owned intents. The plugin supplies a capability; its contract alone does not define a useful workflow.
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
