Appearance
Status: stable — public glossary of 0.8.0 canonical terms, as amended on 2026-07-28. Status per term: frozen = stable canonical wording; open = concept accepted, semantics undecided; retired = no longer canonical.
Glossary
Core platform
| Term | Status | Definition |
|---|---|---|
| Xtrape Platform | frozen (topology open) | The shared management and governance plane tools connect to instead of building independent management planes. Owns admission, registry, resolution, authorization integration, invocation coordination, and audit. Logical authority does not prescribe process count, clustering, or deployment topology. |
| Interaction Layer | frozen | The Platform concept covering interaction products (Panel, Exposure, Telegram/Channels, future products). These products own no independent registry, repository, authorization, or runtime state. |
| Panel | frozen | The web operator UI interaction product; operational control-plane responsibility is implemented by Platform modules, not owned by the UI. |
| Connector | core component; topology placement open | A core platform component bridging an external runtime, environment, or system into Xtrape — like Panel and Exposure, part of the platform's own component set, not an Artifact type. Not an AI agent, not a Service peer, not automatically a Participant. |
| Telegram / Channels | frozen | The conversational interaction product for entry, notification, approval, and lightweight action — parallel to Panel and Exposure. |
Exposure family
| Term | Status | Definition |
|---|---|---|
| Xtrape Exposure | frozen | The AI-facing capability-disclosure interaction product: Exposure Tasks, Skill references, Task Templates, and protocol projections (MCP first). Owns AI-facing naming, discovery, and projection snapshots — never authorization. |
| Exposure Task | frozen | A stable, versioned, protocol-neutral definition of reusable work presented to an AI client. Not a running task, a grant, an Action, a Command, or a Checkpoint. |
| Controlled Exposure | frozen | The platform-wide governance model deciding what is projected and who may invoke it. Distinct from the Xtrape Exposure product. |
| MCP Protocol Projection / Xtrape MCP | concept frozen; component identity open | The edition-neutral MCP adapter role under Exposure that serializes the Platform-authorized tool projection. MCP is a projection, not a Device and not a layer. |
Artifacts
| Term | Status | Definition |
|---|---|---|
| Artifact | frozen | Umbrella for reusable, creatable, referenceable, potentially distributable work products. Types: Widget, Skill, Component, Script, Snippet, Source Code. Implies neither runnability nor publication. |
| Artifact Repository | frozen | The product surface that stores, versions, discovers, and distributes Artifacts; may index external hosts and registries without replacing them. |
| Widget | frozen | The deployable/runnable Artifact type; Widget → Service on start/deploy. Identity is independent of review, signing, publication, or admission states. |
| Skill | frozen | An Artifact carrying reusable procedural guidance for an AI. Referencable from Exposure Tasks; never executable authority. Not a synonym for Capability. |
| Component | frozen | An Artifact type for reusable building blocks. |
| Script / Snippet / Source Code | frozen | Artifact types for executable script material, small reusable fragments, and source material respectively. |
| Repository / Mine / Created | frozen | The canonical navigation views: discoverable / obtained-or-manageable / authored (Created ⊂ Mine). None implies running or published. |
Runtime and execution
| Term | Status | Definition |
|---|---|---|
| Service | frozen | The running, configured, governed capability created when a Widget is started or deployed, and the user-visible execution role — there is no separate actor object. Corresponds to one registration token. To the system it is a logical grouping and task entry point, created by the Platform when the first Worker registers with that token; it executes nothing itself — its Workers do. Not the Widget artifact; not a generic synonym for "deployable". |
| Worker | frozen | The execution unit a Service uses to perform work, and the entity that actually runs and executes. A Service is a set of Workers sharing one registration token. Not a synonym for Service, Widget, Connector, or deployment target. Its Chinese rendering is an open decision. |
| Replica | frozen | The technical-domain synonym of Worker — the same thing in another register, admissible in orchestration and scaling text. Never modeled as an independent object or given its own lifecycle. |
| Capability | frozen | Exactly the grouping of Actions a Service provides — Service → Capability → Action — and nothing more. A semantic grouping boundary, not an independent runtime object: not invoked, no lifecycle of its own, not a second name for Service. |
| Action | frozen | A concrete named operation under a Capability; the authorization granularity. |
| Command | frozen | A concrete request expressing intent to execute an Action. |
| Event | frozen | A recorded fact or state change. Command is intent; Event is fact. |
| Checkpoint | frozen | An immutable, versioned, schema-bound, policy-governed operation published by a Service. Runtime authority always resolves to exact immutable Checkpoint versions. |
| Resource | frozen | The canonical target a Checkpoint operates on. Authorization is evaluated against Checkpoint and Resource together. |
Credentials
| Term | Status | Definition |
|---|---|---|
| Account Token | frozen | The Account-scoped delegation credential created for use through a Device. It represents the Account and its delegated scope, and may only narrow Account and system authority. |
| Service Token | frozen | The workload credential proving a Service's runtime identity. One Service Token corresponds to one Service and is shared by all of that Service's Workers — the token is what makes several Workers one Service. Distinct from the Account Token. |
Retired terms
| Retired term | Replacement |
|---|---|
| Runner | Worker — the English object definition (the execution unit a Service uses) moved there on 2026-07-28. Not an Xtrape object-model term any more, and not to be reintroduced. Unrelated homonyms stay valid: CI/CD runners and third-party product names are not this concept. |
| Agent (top-level object) | Connector where the meaning was bridging an external runtime; Worker where it meant the running instance; Service Token where it meant the workload credential (formerly "Agent Token"). AI-agent-as-caller awaits the Participant model. Out of scope of all of these: the exposure-side principal type naming an autonomous AI originator — that names who initiated an invocation, not what runs or what bridges, and it is not renamed. Deployment/target agents and the ordinary phrase "AI agent" are likewise untouched. |
| Service Instance (as an entity) | Worker — the registered running instance the 0.7.x registration contracts describe is the Worker; it was never a further object between Service and Worker. The ServiceInstance / instanceId wire and storage identifiers are frozen bytes and stay: read "Worker" for the concept, keep the identifier verbatim. |
| Asset (work-product umbrella) | Artifact; where the old word meant an authorization target or runtime-managed object, Resource or the owning governance concept. Reviewed by meaning, never blind-replaced. |
| Store / Xtrape Store | Artifact Repository. |
| Installed | Obtained → Mine; authored → Created; running → Service. |
| Gateway / gateway-to-gateway | Platform module interfaces; Platform-to-Platform for multi-platform collaboration. |
| UX (architecture node) | Interaction Layer; "UX" remains ordinary product-design vocabulary only. |
| Node / Center / Capsule | The Platform concept; Capsule survives only as legacy compatibility identifiers. |
| Package (top-level object) | The delivery/serialization/build representation of an Artifact or Widget; wire representation is an open decision. |
Naming rules worth knowing
- Concept before implementation. Product concepts, repository names, and package names are separate identity layers; architecture is never inferred from a package name.
- Server → Platform is a concept rename ("Xtrape Platform", "Platform-to-Platform"); physical repository/package renames run on their own compatibility cadence.
- Do not infer originator type from access surface. A Panel request is not automatically human; an MCP request is not automatically autonomous AI.
- A concept rename is not a wire change. When a term is renamed, already-issued credential prefixes, field names, and route paths stay as frozen bytes; only the concept name moves. Read the current concept, keep the identifier verbatim.