Unclassified
Product Package Runtime
Status: Normative
Date: 2026-08-11
Parent: INTEGRATEWISE_ARCHITECTURE_v2.2.md
A Product Package is the reusable runtime unit that turns host-connected systems into governed business context and executable Tool Capabilities for a Workbench.
Components
| Component | Owns | Does not own |
|---|---|---|
| Discovery | packages, projections, schemas, MCP endpoints, capabilities, versions, health | provider credentials |
| Capabilities | typed/versioned effective operation registry and resolution | executing operations |
| Spine Cache | fast rebuildable materialized operational state | canonical history |
| ADK | stable runtime/developer APIs for context, capability invocation, lifecycle, policy hooks, errors and telemetry | durable truth or credentials |
| Orchestrator | durable workflow sequencing, retries, compensation, approvals, service/tool/agent tasks | Governance policy authority |
| Business Context | canonical semantic entities, relationships, assertions, provenance and temporal validity | ephemeral model speculation |
| Loader | extraction, pagination, webhooks, cursors, raw envelopes, checkpoints and replay | canonical semantics |
| Normalizer | canonical mapping, validation, deduplication, identity resolution and lineage | provider auth |
| MCP Connector | governed MCP lifecycle, translation, resources/tools and policy enforcement | bypassing Tool Capability policy |
| Tool Capability | executable typed operation with schemas, policy, side-effect class, version, idempotency and audit contract | autonomous authority |
Package contract
A releaseable Product Package should carry versioned definitions for:
- manifest and compatibility ranges
- connector projection rules
- capability catalogue
- canonical schemas and mappings
- loader/normalizer definitions
- Tool Capability input/output schemas
- MCP bindings
- policy defaults
- Workbench projection metadata
- migrations
- certification/contract tests
Context flow
host connector projection
→ Loader
→ raw/replayable envelope
→ Normalizer
→ Business Context candidate
→ governed promotion
→ canonical truth
→ Spine Cache materialization
→ Projection Engine
→ Workbench
Execution flow
Workbench/Twin/workflow intent
→ capability resolution
→ Tool Capability
→ Governance
→ Orchestrator/Hermes
→ host/provider/internal service
→ result
→ reconciliation
→ canonical outcome
Connector-aware routing
Discovery, Capability resolution, Loader, Normalizer, MCP Connector and Tool Capability execution must resolve against the current connector projection and effective-grant state. Provider assumptions must not be hard-coded into configuration or activation paths when registry-based routing exists.
Package lifecycle
Draft → Validated → Certified → Published → Installed → Activated
→ Upgraded/Deprecated → Retired
Activation is tenant-specific. Package artifacts are reusable; tenant credentials, data, queues, caches and evidence are not package artifacts.