{"slug":"business/51-glossary","title":"Glossary","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/51-glossary.mdx","bytes":4004,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nUse these definitions when writing integrations, reviewing proposals, or debugging IntegrateWise behavior.\n\n- Adaptive Spine: The canonical context and continuity network that owns operational truth.\n- Active Context Bundle: The product-language name for the ContinuityBundle delivered to runtime.\n- Approval Center: The user-facing governance surface for reviewing, approving, rejecting, delegating, and dispatching proposals.\n- API Connector: Structured external system connectivity for REST, GraphQL, and gRPC.\n- API Wrapper: A normalized capability adapter for non-standard or legacy external APIs.\n- Approval Token: The minted evidence that a proposed consequential action passed governance.\n- Canary Context: Use only if defined in tenant policy; otherwise do not conflate with canonical test data.\n- Capability Fabric: The resolver that maps available adapter capabilities into actionable platform actions under policy.\n- Common Connected Surface: The logical operational layer across independent connected systems. Logical, not a datastore.\n- Compact Load: Not a canonical term; use Creamy, Delta, or Streaming Load.\n- Config Version: The immutable monotonic identifier tied to a CompiledTenantConfig snapshot used for execution-plan pinning.\n- Continuity Bridge: The separate contract that delivers the Active Context Bundle to runtime.\n- Contract: A strict typed interface declaring required capability, inputs, and expected output format.\n- Creamy Load: Deep initial hydration for historical continuity formation.\n- Customer Zero: IntegrateWise internal operations using the full stack.\n- Delta Load: Time-window polling ingestion that absorbs ongoing changes.\n- ExecutionPlan: The immutable, approved, versioned plan describing exact steps, authority, evidence, impact, and rollback for a consequential action.\n- Hermes: Execution coordinator only; receives authorized ExecutionPlans and dispatches runtime adapters.\n- Integration Manager: Governs connection lifecycle, auth, MCP discovery, webhook termination, and transport health. Limited to ConnectionProviderRegistry.\n- MCP Connector: Model Context Protocol path for dynamic tool, resource, and prompt exposure under governed interception.\n- Memory Fabric: Tiered memory system covering Working Context, Candidate Memory, and Promoted Memory.\n- OODA: Observe, Orient, Decide, Act. Internal operating model, not usually surfaced to users.\n- Outcome Event: The completed execution result emitted after provider confirmation, sync, and promotion evaluation.\n- Plan Builder: Creates immutable ExecutionPlans from proposals, capability contracts, and governance decisions.\n- Pre-Proposal Gate: Authority, scope, and policy check before proposal execution.\n- Post-Proposal Gate: Risk, evidence, confidence, and approval requirement check after proposal creation.\n- Provider Registry: Directory of active, authenticated adapters with lifecycle state and health signatures.\n- Promotion: The capability-aware, governance-aware decision to adopt resulting provider state as canonical Spine truth.\n- Projection: A governed view assembled from Spine state for Workbench consumption.\n- Runtime Adapter: Lowest-level transport or compute environment executing dispatched commands under sandbox and isolation boundaries.\n- Secrets Provider: Resolves credentials just-in-time for adapter use.\n- Spine: Short form for Adaptive Spine.\n- Streaming Load: Continuous event-driven ingestion from webhook or queue sources.\n- Sync Engine: Bidirectional reconciler between the State Substrate and external providers.\n- Tenant Isolation: Hard partition boundary enforced programmatically at provider and query layers.\n- Twin: Silent partner that prepares outputs, detects change, retrieves context, and proposes actions. Does not execute consequential actions independently.\n- Universal Governance: The cross-phase authority boundary enforcing pre- and post-proposal checks.\n- Workbench: The primary compositional operating hub by department or role.\n"}