Glossary
| Term | Meaning |
|---|---|
| App / Connector | A registry entry describing an integration and how the platform loads + invokes it |
| Deployment | How the platform reaches the app: lambda, bundled (npm/Maven connector artifact) or external (HTTP) |
| Invocation target | How a connector app reaches the downstream/target system it fronts |
| Capability | A labelled feature an app provides; PAYMENT is the only one with an enforced contract |
| Capability contract | Declared required operations/config keys for a capability (e.g. payment-v1) |
| Interface | A named + versioned API contract (e.g. PaymentProcessorV1) an app implements |
| Enablement | Turning an app on for a business and/or store (per interface); first per interface = default |
| Config override | A layered (business/store/service) partial config deep‑merged into the effective config |
| serviceInstanceMap | Map of consuming service name → that service’s instance id, required before enabling |
| Drain | Graceful wind‑down: reject new work, finish in‑flight |
| Canary | Gradual traffic rollout with auto‑promote/rollback based on error/success thresholds |
| Self‑registration | Machine‑to‑machine app registration via API key or CI/CD app.deployed event |
| Privilege | A marketplace:* string checked against JWT claims |
| Effective config | Fully merged configuration returned to consumers for a business/store/app |
| Approval workflow | The draft→pending→approved→deprecated→archived (+rejected/deleted) lifecycle |
Items flagged “NOT CURRENTLY ENABLED / not wired” are present in the codebase but not reachable at runtime as of this revision.
Revision History
2026-08-05 | JP – Created the page and added the content.