Current

IntegrateWise — Technical Glossary

Version: 1.0 | Date: 2026-08-23 | Status: ACTIVE
Authority: Nirmal (Founder)

Every technical term, product concept, and domain vocabulary used in the IntegrateWise / Spine Workspace codebase.


Naming Hierarchy & Identity

TermAssociation
IntegrateWiseThe company/brand. Maker of SpineWorkspace.
SpineWorkspaceThe product. Domain spineworkspace.com. Self-organizing workspace where people and AI continue and complete work.
WorkbenchThe user's single operational surface inside SpineWorkspace. Role-specific projection of work and context.
Customer ZeroIW's own production tenant used to prove the package before external publication.
IW-Spine-NetworkLocked public distribution identity for marketplace artifacts.
IW-Spine-Network PluginMCP-backed app with focused embedded UI for Plugin marketplace/directory.
IW-Spine-Network MCPRemote MCP server exposing exactly 19 public tools for MCP marketplace/registry.

The 12 Kernel Terms

TermAssociation
WORKA human or machine moving an objective through state.
CONTEXTThe minimum relevant connected state required to understand current work.
SPINEThe canonical connected model of operational work state. System of record for entities, context, decisions, signals, proposals, approvals, outcomes.
CONTINUITYPreservation and bounded transfer of relevant context across time, systems, humans, and agents.
WORKBENCHThe role-specific projection of work and context presented to a human.
TWINNon-authoritative cognitive participant that consumes grounded context. The user's primary AI representative.
CAPABILITYA registered operation that may read, derive, or change work state.
GOVERNANCEThe authority that determines whether a capability or proposed consequence is permitted.
HERMESThe execution coordinator for authorized capability invocations.
SYNCReconciliation of resulting state across connected systems.
BRIDGEThe governed exchange boundary through which an authorized consumer receives or contributes bounded continuity.
OUTCOMEThe observed result of work or execution that may become new canonical state.

OODA Grammar & The Four Buttons

TermAssociation
OODAObserve-Orient-Decide-Act control grammar. The only OODA control grammar for truth capture, Twin reasoning, delegation, and governed execution.
Store in SpineObserve button. User captures truth through governed Pipeline; Spine records entity, timeline, provenance.
Ask your TwinOrient button. User asks Twin to understand the work; Twin reads bounded context then reasons.
Assign your TwinDecide button. User delegates intent to Twin; Twin creates draft/proposal but does NOT execute until approved.
Approve Twin's ActionAct button. User authorizes execution; Governance validates, Pipeline invokes, outcome reconciled to Spine.
Four ButtonsThe explicit OODA control grammar — the only way to interact with Twin for consequential operations.

Four Operational Patterns

The fundamental ways the workbench operates to enable human-AI collaboration. Not UI buttons — operational contracts.

PatternAssociation
Store in SpineAll business context, communications, decisions, and evidence are automatically captured into Spine Fabric. The organizational memory both humans and AI access.
Ask Your TwinHuman queries Twin through the workbench. Twin has access to full business context from Spine. Bidirectional — human can ask, Twin can proactively suggest.
Approve Your TwinTwin's proposals require human authorization for governed actions. Triggers: capability resolution → governance check → source system write → receipt → reconciliation. HITL by design.
Reject/Redo Your TwinHuman can reject Twin's work. Twin retries with new context or escalates. System reconciles state. Ensures continuity, prevents hallucinations from cascading.

Mapping to OODA

Operational PatternOODA PhaseButton
Store in SpineObserveStore in Spine
Ask Your TwinOrientAsk your Twin
Approve Your TwinDecideAssign your Twin
Reject/Redo Your TwinActApprove Twin's Action

Doctrines & Laws

TermAssociation
Twin LawTwin is a capability of the Workbench, not a panel.
Context LawThe human never explains already-known work context to AI.
Memory LawSpine owns truth. Memory informs truth. Memory is not truth.
Authority LawConfidence increases trust. Confidence never grants authority.
Silence LawTwin prefers silence over low-value commentary.
Capability LawWorkbench projects tool capabilities, does not duplicate tools.
Bridge LawOne platform. One boundary. Different projections.
Product-Platform LawBroad underneath. Narrow at the surface.
Same-Artifact LawCustomer Zero and external customers use the same build.
One-Way Promotion LawPromote only code/manifests; never tenant data/credentials/state.
Customer Zero Proof LawCZ must run daily work through Plugin and browser Workbench.
Clean-Tenant LawFrozen versions install into unrelated tenant without code changes.
Governed Execution LawEvery external action requires approval token, Hermes execution, audit, reconciliation.
Compatibility LawRelease manifest records compatible versions.
No Second FortressNo product deployment becomes an independent authority plane.

15 Canonical Spine Laws

#Law
1No model owns truth
2No agent bypasses Twin
3No capability bypasses Governance
4No frontend owns canonical state
5No product owns credentials
6No source-system mutation without receipt
7No ambiguous retry
8No context without authority
9No observation without identity
10No isolated agent memory
11No second Fortress
12No disconnected execution
13No hidden incompleteness
14No package authority
15No provider-specific business UX

14 Product Doctrines

Business need first, One View, One Twin, Agents are workers, Spine is contextual infrastructure, Context is shared, Handoffs are contextual, Capabilities are discoverable, Authority is explicit, Models do not own truth, Source systems remain execution authorities, Every meaningful action returns to Spine, Ask/Approve/Reject/Redo is native, More connected work strengthens Spine.


Spine Fabric & Storage

TermAssociation
Spine FabricThe organization's persistent business-context substrate. Collection of storage and memory mechanisms, not one database.
Canonical PlaneProtects authoritative truth in Spine; governed writes only.
Operational PlaneWorking/contextual projections + memory for Workspace, Twin, agents, workflows.
Canonical TruthAuthoritative business truth — entities, relationships, transactions, KPIs.
Operational MemoryEvents, context, embeddings, semantic memory, active work state.
Adaptive SpineThe runtime realization of Spine with 7 canonical entity types.
FortressLegacy term for Supabase Postgres database used as canonical SSOT (historical/retired).
D1Cloudflare D1 — per-tenant operational Spine database; bounded edge state.
KVCloudflare KV — hot cache for rate limits, sessions, connector status, signal cache, metrics, OAuth state.
R2Cloudflare R2 — blob storage for files, attachments, evidence, raw payloads.
VectorizeCloudflare Vectorize — embedding storage for semantic search.
AI SearchCloudflare AI Search — tenant-scoped semantic search over memory/knowledge.
Durable ObjectsCloudflare Durable Objects — agent memory with snapshotting to D1.
Neon PostgresCanonical control-plane authority; owns canonical operational entities, relationships, lineage.
Six-Layer Storage FabricL1 Postgres/Neon/D1, L2 Redis/KV, L3 R2, L4 Conversational Store, L5 Vectorize/pgvector, L6 Durable Objects.

Pipeline & Flows

TermAssociation
PipelineData processing pipeline: LOAD → NORMALIZE → STORE → THINK → APPROVE → ACT → REPEAT.
Flow AStructured operational data — deterministic normalization, governed writers, Pipeline promotion.
Flow BUnstructured business data — documents, communications, attachments, transcripts.
Flow CAI/agentic activity — never writes directly to Spine; Triage proposes promotion.
Flow DIdentity/authorization gate — tenant, workspace, role, configuration, connection, credential, capability, policy binding.
Normalizer6-stage data normalization kernel: NA0 Schema Detector → NA1 Canonical Transformer → NA2 SSOT Binder → NA3 Lineage Manager → NA4 Relation Binder → NA5 Spine Publisher.
LoaderIngests raw source data into the pipeline.
TriageAdaptive classifier/router for incoming information. Receives, validates, classifies, redacts, deduplicates, links, quarantines, stages. Cannot independently decide truth.
Memory PromoterEngine that promotes selected Spine entities into Memory based on 7 Promotion Signals.
Promotion Signalsimportant, repeated, strategic, behavioral, decision, preference, exception.
Spine WriterThe governed sole-writer path to canonical state.
Deterministic Normalization8 stages: Raw Event Ingestion, Canonical Field Mapping, Schema Normalization, Entity Resolution, Deduplication, Relationship Linking, Depth Matrix Evaluation, Spine Write.
Depth MatrixTenant schema configuration controlling how deep normalization/relationship traversal goes.
Transactional OutboxDomain write + outbox event happen atomically in D1; outbox publisher pushes to Cloudflare Queue.
IdempotencyDeduplication mechanism using processed_commands table; reused idempotency key with different payload = conflict.

Capability Fabric

TermAssociation
Capability FabricGoverned execution language between intelligence and operational action. Discovers, selects, validates, enforces governance, routes execution.
Semantic CapabilityWhat a human or Twin means, expressed without any provider (e.g., email.send, crm.account.update).
Tool CapabilityVersioned provider binding of a semantic capability (e.g., gmail.email.send@2).
ResolvedCapabilityFully bound triple: SemanticCapability + ToolCapability + ConnectionId. Nothing downstream may re-pick.
CapabilityRegistryRegistry of semantic capabilities and tool capabilities.
FabricCapabilityResolverResolves intent to resolved capability through registry + connections.
CapabilitySurfaceItemContextual, human-readable description of one capability for Workbench rendering.
MCP Pool55 registered capabilities. Pattern: Registry → Resolver → Health → Routing → Versioning.
Provider Management MCP15 capabilities: provider.*, apps.*, connections.*, oauth.*.
Integration Management MCP28 capabilities: connectors.*, sync.*, webhooks.*, schemas.*.
Task Management MCP12 capabilities: tasks.*.
EffectSignatureWhat one invocation of a tool capability changes in provider reality.
RiskClassread, low, medium, high, critical — classification of capability risk.
Reversibilityreversible, compensatable, irreversible — whether an action can be undone.
ConnectionTenant-owned, credentialed instance of a connector definition.
ConnectionStatushealthy, degraded, expired, revoked, unavailable.
EntitlementLevelnone, starter, growth, enterprise, unknown — access tier.

Governance

TermAssociation
GovernancePolicy and approval semantics — the operational control plane for whether actions may advance.
GovernanceDecisionDeterministic outcome: allowed, approval_required, or blocked.
PolicySnapshotPolicy state a decision was made against; snapshotting makes decisions reproducible and auditable.
HITLHuman-in-the-Loop. Governance behavior where operators act as reviewers, approvers, escalators, or exception handlers.
ApprovalStatedraft, proposed, awaiting_human_review, approved, rejected, modified, deferred, executing, outcome_received, verification_required, verified, reconciled, closed.
AuthorityDecisionRecord of a human decision on a proposal.
ProposalLifecycleFull lifecycle of a proposed action from creation through verification.
Approval TokenScoped human approval token minted by Governance; required for every external execution.

Agents & Intelligence

TermAssociation
Twin OrchestratorCognitive orchestration layer. Observes, reasons, proposes, coordinates. The primary AI representative.
Three-Tier Agent TaxonomyPrimary Orchestrator (Twin), Cognitive/Governance Services (Triage, Governance, Entity Resolver, Evidence), Specialized Platform Workers (Schema Generator, Schema Orchestrator, Coworker Agent, Adaptive Auto-Tuner).
Triage AgentReceives incoming information, validates, classifies, routes. Cannot decide truth independently.
Coworker AgentPerforms preparation and bounded delegated work. Proposes only.
Schema GeneratorProposes entities for schema-discovery coordination.
Schema OrchestratorMaps/checks diffs in schema proposals.
Adaptive Auto-TunerRefines thresholds. Propose-only worker.
Entity ResolverCognitive service that resolves entity references during Orient/Decide.
EvidenceBounded service Twin calls during Orient/Decide.
Agent RegistryInfrastructure service tracking available agents.
Tenant Brain DODurable Object for tenant-level governance and cognitive state.
ColonyAgent colony pattern for multi-agent runs.
Morning BriefScheduled 7am daily briefing from Twin.

Identity & Auth

TermAssociation
One AuthSingle ecosystem entry for identity; host authority never duplicated.
One AccessMFE for identity, tenant/workspace context, sessions, consent, scoped grants, connector marketplace.
TenantIsolated customer environment. Every durable record carries tenant_id. Per-tenant D1 routing.
TenantGateGateway-enforced tenant boundary; every query binds tenant_id first.
WorkspaceOrganizational subdivision within a tenant; role-specific projection surface.
PrincipalContextIdentity and authority derived by Gateway from the One Access session.
ActorContextActor/authority context resolved by One Auth; never supplied by a browser.
Credential WallWhere credentials and access tokens remain; never published to listing, browser, or MCP tool result.
ClerkPrimary authentication provider (JWT, OAuth).
DescopeAlternative auth provider for server-side session validation.
Cloudflare AccessMCP Auth provider.
RLSRow-Level Security. PostgreSQL RLS enforcing tenant_id isolation.
WorkspaceRoleowner, admin, member, analyst, guest.
DomainIdintegratewise-apac, personal, account-success, revops, salesops.

Context & Memory

TermAssociation
ActiveContextBundleOne bounded, authorized context response for a work context.
Context AssemblyFirst-class system operation resolving relevant context for a business need.
Context ResolverAssembles User, Work, Organization, Entity, Event, Document, Conversation, Transaction, Policy, and Capability context.
Context BundleAssembled context delivered to Human View and Twin Reasoning.
ContextScopeentity, relationships, knowledge, memory, evidence, capabilities, entity360, ai_output.
EntityContextDisclosure available regardless of Entity 360 maturity.
Entity 360Single entity continuation view with activity, intelligence, action, governance, execution state, and continuity.
Entity 360 ProjectionOptional, policy-gated projection requiring full Entity 360 maturity.
Entity 360 FormationProcess of building Entity 360 from resolved related entities, evidence, provenance.
FreshnessSummaryData freshness: live, recent, stale, historical, mixed, unknown.
Memory ScopesUSER (per-person), WORK (per-entity/process), ORGANIZATION (tenant-wide).
Org MemoryOrganizational memory stored in D1; promoted from Spine via Promotion Signals.
Continuity BridgePlatform concept: operational reality → continuity capture → persisted state → context recovery → next actor context.
Workspace Discovery ProjectionFirst browser read: GET /api/v1/workspace/discovery — versioned, tenant/RBAC-scoped manifest.
ContextGatewayAssertionHMAC-signed claim asserting Gateway-resolved identity for context requests.
Canonical Memory FabricPlatform-owned memory holding Working Memory and Agent Memory.
Working MemoryShort-term operational memory in Durable Objects.
Agent MemoryLong-term agent state in Durable Objects, snapshotting to D1.

Projection & Workbench

TermAssociation
Projection EngineAssembles workbench projections from Spine data.
ProjectionEventEvent for projection snapshot, update, invalidation, execution outcome, notification, twin stream.
ProjectionChannelprojection.snapshot, projection.update, projection.invalidation, execution.outcome, notification.event, twin.stream, command, query, approval, presence.
WorkbenchCommandCommand from Workbench surface to platform.
WorkbenchShellTop-level layout and context switching.
L1Internal engineering label for Workbench UI layer — never user-facing.
L2Internal label for Cognitive overlay (Twin).
L4Internal label for Continuity/Memory layer.
L7Internal label for Governance layer.
Five Zone ShellWorkbench layout structure.
Role-Based WorkbenchRole-specific workbench rendering.
Department WorkbenchDepartment-specific workbench.
OODA ButtonsUI component for the Four Buttons.
Twin Signal FeedInline signal display from Twin observations.
Store Spine ModalUI for Store in Spine action.
Context Action SlotGoverned action component for context-aware actions.
Proposal Approval CardUI for Twin proposal approval.

Services

TermAssociation
GatewaySingle entry point for ALL requests. Validates JWT, resolves tenant, rate limits, routes to correct service.
ConnectorManages connections to external systems; sync, capability routes.
Connector SyncHandles initial hydration and delta sync for connectors.
PipelineData pipeline: normalize, spine write, memory promotion.
IntelligenceThink + Act + Govern + Agents cognitive layer.
KnowledgeKnowledge management service; search, embed, synthesize.
HermesExecution orchestrator for authorized capability invocations.
StoreFile uploads, R2 storage, processing pipeline, version management.
SignalsSignal event bus with event sourcing; observe, replay, pattern matching.
ContinuityPersistent operational context service.
Twin OrchestratorCognitive orchestration: observe, reason, propose, coordinate, learn.
LoaderRaw data ingestion into the pipeline.
NormalizerData normalization service.
GovernGovernance service.
ActAction execution service.
ThinkCognitive thinking service.
AdminAdmin operations service.
BillingBilling management service.
TenantsTenant management service.
Webhook IngressWebhook ingestion and real-time broadcasting.
MCP ConnectorPublic 19-tool Spine MCP / semantic continuity boundary.
MCP PoolMCP capability pool with 55 registered capabilities.
TelemetryApplication telemetry service.
Agent RegistryAgent registration and discovery.
IW Agent RuntimeAgent runtime with Durable Objects.
Task ManagementTask CRUD, scheduling, cron, handlers.
Provider Management MCPProvider, app, connection, OAuth management.
Integration Management MCPConnector, sync, webhook, schema management.
Folder WatcherBridges local filesystem changes into pipeline.
HuggingFace InferenceHuggingFace model inference service.
Projection ServiceProjection management service.

Packages

TermAssociation
@integratewise/kernelUnified Kernel Connector connecting MCP with Spine, ADK, Orchestrator, Discovery.
@integratewise/orchestratorExecution engine managing capability execution across agents, connectors, MCP tools.
@integratewise/capabilityCanonical Capability Fabric runtime contracts.
@integratewise/projection-contractsCanonical types for Projection Engine and Workbench command bus.
@integratewise/normalizer6-stage data normalization kernel.
@integratewise/spine-entities7 canonical entity types for the Adaptive Spine.
@integratewise/spine-networkIW Spine MCP Server connecting AI tools to IW ecosystem through the Spine.
@integratewise/context-contractsActive Context Bundle and Entity Context contracts.
@integratewise/gateway-sdkGateway client SDK with spine-tools.
@integratewise/model-gatewayModel registry and provider management.
@integratewise/analyticsAnalytics hooks and providers.
@integratewise/webhooksWebhook worker for incoming events.
@integratewise/acceleratorsAccelerator packs for different business domains.
@integratewise/bootstrapBootstrap and initialization package.
@integratewise/contractsShared contracts including authority doctrine, surfaces, wiring constants.
@integratewise/handoff-adaptersHandoff adapters with idempotency and JSON adapters.
@integratewise/workbench-configRole configs, sidebar navigation, projection profiles.
@integratewise/design-systemDesign system components and utilities.
@integratewise/skillsSkills definitions.
@integratewise/typesShared TypeScript types.
@integratewise/configConfiguration including env bindings.
@integratewise/core/governance-engineCore governance engine with approval queue.
@integratewise/coda-packCoda integration pack with sync tables and actions.

Canonical Spine Entities

TermAssociation
ConnectionTenant-owned, credentialed instance of a connector.
ConnectorConnector definition with capabilities.
SyncJobSynchronization job tracking.
WebhookWebhook registration and statistics.
SchemaSchema definition.
CapabilityCapability definition with policy.
TimelineEventTemporal history of entity mutations; append-only.
PlatformEventCross-service event with causation, correlation, idempotency.

Execution & Reconciliation

TermAssociation
ExecutionPlanImmutable plan created before Governance evaluation; carries content hash.
ExecutionStepSteps: connector_call, agent_invoke, mcp_tool, spine_read, spine_write, approval_gate.
ExecutionLifecycleStatedispatched, provider_acknowledged, reconciling, reconciled, partially_reconciled, reconciliation_failed, promoted.
ReconciliationResultComparison of expected effects vs observed provider reality.
ObservedEffectEffect actually observed from provider read-back or event.
EffectMatchComparison result for one expected effect.
PromotionEnvelopeEnvelope consumed by Pipeline for canonical promotion; only promoted when reconciled.
ContinuityChainEvery identifier needed to reconstruct a continuity chain from one record.
RuntimeResultHealth/error result type for capability operations.
StructuredErrorTyped error for capability operations.
Canonical JSONDeterministic JSON serialization for content hashing.
PlanHashSHA-256 over every plan field; re-derived downstream to detect tampering.
CapabilityIntentUser or Twin intent before any provider is chosen.
WorkServiceHuman operational work: tasks, queues, assignments, deadlines, ownership.
ExecutionServiceMachine execution: provider dispatch, invocation attempts, retries, compensation.

Projections & Workspace

TermAssociation
RoleConfigRole definition: id, label, sidebar modules, connected systems, AI capabilities, operational features, MCP capabilities, Spine projection.
ModuleIdSidebar module identifier.
PlatformCapabilityShared platform modules: integrations, configuration, activation, governance, continuity, network-graphs.
CTXEnumCTX_CS, CTX_SALES, CTX_SUPPORT, CTX_PM, CTX_MARKETING, CTX_BIZOPS, CTX_TECH, CTX_HR, CTX_FINANCE, CTX_LEGAL.
16 Canonical SectionsHome, My Work, Entity Database, Entity 360, Pipeline/Queue, Timeline, Calendar, Communications, Documents & Knowledge, Signals & Risks, Approvals, Planning Canvas, Reports & Metrics, Automation & Playbooks, Recent Work, Twin.
15 Business Domain WorkbenchesAccount Success, Technical Account Success, Service, Support, Sales, Marketing, Content, Finance/RevOps, Product Engineering, Business Operations, Operations, Founder Ops, Human Resources, Legal, Personal.

Four Planes

TermAssociation
Experience PlaneUser Workbench, Twin, Admin, Mobile, AI Chat, Model Selector, Agent Canvas.
Intelligence PlaneHermes, Knowledge, Memory, Signals, Model Gateway, Omni Router.
Execution PlaneGateway, MCP Pool, Provider MCP, Integration MCP, Task MCP.
Foundation PlaneAdaptive Spine, Identity, Security, Storage, Timeline, Provenance.

Two Capability Planes & Membranes

TermAssociation
Tool/Operational Capability Plane"What happened / what can execute". Reads/mutates provider data; emits Action Receipts.
Cognitive Capability Plane"What might this mean". Models/rerankers/embeddings/Twin; candidate proposals only ("rented cognition").
Membrane A (Truth Egress)Context Assembler redacts/restricts Spine context reaching cognitive models.
Membrane B (Truth Promotion)Cognitive candidates pass Evidence Attachment → Triage → Governance → Human Approval before promotion.

Data Concepts

TermAssociation
ProvenanceSource and lineage of data; mandatory in universal record envelope.
LineageSource, source_id, event_id, timestamp trail.
Canonical FieldsAllowed fields per entity type for normalization.
Schema NormalizationTransforming raw data into canonical format.
Entity ResolutionMatching/merging entities across sources.
DeduplicationRemoving duplicate records.
Relationship LinkingConnecting related entities.
Canonical Entity Typesaccount, contact, opportunity, deal, project, task, document, meeting, email, message, event, signal.
Universal Record Envelopeid, tenant_id, workspace_id, status, version, origin, confidence, source_connection_id, provenance, metadata, created_by/at, updated_by/at, archived_at — shared by every operational table.

Marketplace & GTM

TermAssociation
Plugin MarketplaceExternal acquisition and embedded activation for AI hosts.
MCP MarketplaceExternal acquisition and tool-first activation.
Connector MarketplaceIn-product capability activation and expansion.
Provider MarketplaceProvider-native IW packages when provider OAuth/webhook semantics require it.
MarketplaceInstallationState machine: initiated → identity_required → workspace_required → consent_required → binding → hydrating → active.
Activation HubOnboarding completion and intelligence activation.
Integration ManagerConnectors, sync, webhooks, schemas management.
Configuration ManagerTenant schema, depth matrix, policies.
Capability ManagerMaps connectors/tools into governed, permissioned capabilities.
North-Star MetricTime to first approved governed outcome.
Claims Maturity ModelDefined / Implemented / Live-verified — code presence alone never satisfies a claim.

Frontend Six Concepts

TermAssociation
EntityOperational data entity.
ProjectionRole-specific view of entity data.
CapabilityAvailable operation.
SignalAttention-requiring event.
ContextRelevant connected state.
TwinPrimary AI representative.

Canonical Reference

For the complete operational model, see:


Tagline

"Truth you own. AI you rent. Approval in between."