A package standard for complete intelligent apps that run through shared host capabilities and App Server bridge contracts.
| Contract | Question answered |
|---|---|
| App package | What installable app is this and what does it contain? |
| Entries | Which pages, commands, workflows, artifacts, background tasks, or settings can the host expose? |
| Capabilities | Which host standards and capability surfaces does this app need? |
| Bindings and context | Which Context, Knowledge, Skill, Tool, Connector, Artifact, Evidence, Policy, and QC dependencies must the user or tenant satisfy? |
| Projection | How does a host compile the app into a catalog without inventing a second runtime? |
| Readiness | Which runtime, connector, permission, evidence, and quality gates must pass before the app can run? |
| Role | Start here | Then read |
|---|---|---|
| App author | Quickstart | Runtime package, manifest design, permissions, release. |
| Host implementor | Desktop host conformance | Runtime model, Capability SDK, projection, readiness, security. |
| Standards reviewer | Specification | JSON Schemas, glossary, version notes. |
| Product planner | What is Agent App? | Standards ecosystem boundary, examples, mini-program analogy. |
A current app should be understandable before execution, installable without changing host core, runnable through typed capability handles, observable through RuntimeCore-derived Agent task events, explicit about delivery boundaries, clear about how users install it, and explicit about how lime.agent / lime.workflow calls enter App Server JSON-RPC. It should also follow the shared host model: user state and platform capabilities come from the host, while app-local storage and app backend services stay isolated. If a package cannot explain its entries, permissions, data boundary, runtime assets, task output contracts, external integrations, side effects, human approval boundaries, install mode, runtime bridge, and local storage placement, it is not ready to be distributed as an Agent App.
Every Agent App page in this documentation should help a reader answer four questions: what boundary this concept owns, which manifest or runtime fields express it, how a host should implement it, and what makes it ready for release. If a page only defines a term but does not show its implementation, readiness, or failure mode, treat it as incomplete.
lime.agent / lime.workflow execution.