{"slug":"architecture/PRODUCT_PACKAGE_RUNTIME","title":"Product Package Runtime","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/PRODUCT_PACKAGE_RUNTIME.mdx","bytes":3880,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Normative  \n**Date:** 2026-08-11  \n**Parent:** [`INTEGRATEWISE_ARCHITECTURE_v2.2.md`](INTEGRATEWISE_ARCHITECTURE_v2.2.md)\n\nA Product Package is the reusable runtime unit that turns host-connected systems into governed business context and executable Tool Capabilities for a Workbench.\n\n## Components\n\n| Component        | Owns                                                                                                            | Does not own                     |\n| ---------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------------- |\n| Discovery        | packages, projections, schemas, MCP endpoints, capabilities, versions, health                                   | provider credentials             |\n| Capabilities     | typed/versioned effective operation registry and resolution                                                     | executing operations             |\n| Spine Cache      | fast rebuildable materialized operational state                                                                 | canonical history                |\n| ADK              | stable runtime/developer APIs for context, capability invocation, lifecycle, policy hooks, errors and telemetry | durable truth or credentials     |\n| Orchestrator     | durable workflow sequencing, retries, compensation, approvals, service/tool/agent tasks                         | Governance policy authority      |\n| Business Context | canonical semantic entities, relationships, assertions, provenance and temporal validity                        | ephemeral model speculation      |\n| Loader           | extraction, pagination, webhooks, cursors, raw envelopes, checkpoints and replay                                | canonical semantics              |\n| Normalizer       | canonical mapping, validation, deduplication, identity resolution and lineage                                   | provider auth                    |\n| MCP Connector    | governed MCP lifecycle, translation, resources/tools and policy enforcement                                     | bypassing Tool Capability policy |\n| Tool Capability  | executable typed operation with schemas, policy, side-effect class, version, idempotency and audit contract     | autonomous authority             |\n\n## Package contract\n\nA releaseable Product Package should carry versioned definitions for:\n\n- manifest and compatibility ranges\n- connector projection rules\n- capability catalogue\n- canonical schemas and mappings\n- loader/normalizer definitions\n- Tool Capability input/output schemas\n- MCP bindings\n- policy defaults\n- Workbench projection metadata\n- migrations\n- certification/contract tests\n\n## Context flow\n\n```text\nhost connector projection\n→ Loader\n→ raw/replayable envelope\n→ Normalizer\n→ Business Context candidate\n→ governed promotion\n→ canonical truth\n→ Spine Cache materialization\n→ Projection Engine\n→ Workbench\n```\n\n## Execution flow\n\n```text\nWorkbench/Twin/workflow intent\n→ capability resolution\n→ Tool Capability\n→ Governance\n→ Orchestrator/Hermes\n→ host/provider/internal service\n→ result\n→ reconciliation\n→ canonical outcome\n```\n\n## Connector-aware routing\n\nDiscovery, 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.\n\n## Package lifecycle\n\n```text\nDraft → Validated → Certified → Published → Installed → Activated\n→ Upgraded/Deprecated → Retired\n```\n\nActivation is tenant-specific. Package artifacts are reusable; tenant credentials, data, queues, caches and evidence are not package artifacts.\n"}