{"slug":"architecture/README","title":"IntegrateWise & Spine Workspace — Architecture Documentation Index","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/README.mdx","bytes":12249,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Canonical Authority Index  \n**Version:** v3.0.0-Canonical  \n**Authority Hierarchy:** [`SYSTEM_ARCHITECTURE_CANONICAL.md`](SYSTEM_ARCHITECTURE_CANONICAL.md) → [`INTEGRATEWISE_ARCHITECTURE.md`](INTEGRATEWISE_ARCHITECTURE.md) → Subsystem Constitutions\n\n---\n\n## 1. Master Canonical Authorities\n\nThese documents define the definitive architecture, category positioning, information hierarchy, and execution models across the entire platform.\n\n| Document                                                                                       | Focus & Authority Scope                                                                                                                                |\n| :--------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |\n| [**`SYSTEM_ARCHITECTURE_CANONICAL.md`**](SYSTEM_ARCHITECTURE_CANONICAL.md)                     | **Primary Platform Authority (v3.0.0)** — Complete 6-Layer Stack, 12-Step Loop, Single Context Law, 18 Projections, Governance & Ingress Architecture. |\n| [**`INTEGRATEWISE_CANONICAL_REFERENCE.md`**](INTEGRATEWISE_CANONICAL_REFERENCE.md)             | **Canonical Reference & Doctrine** — 5-Layer Stack, 8 Spine Domains, 6 Storage Substrates, Universal Write Path, and 5-Zone UI grammar.                |\n| [**`INTEGRATEWISE_USER_JOURNEY.md`**](INTEGRATEWISE_USER_JOURNEY.md)                           | **User Journey & Activation Blueprint** — 8 Journey Stages (Enter → Loop) and 7 Activation Readiness Gates.                                            |\n| [**`INTEGRATEWISE_ARCHITECTURE.md`**](INTEGRATEWISE_ARCHITECTURE.md)                           | **Core Subsystem Specification** — Technical architecture, Adaptive Spine substrate, Capability Fabric, Hermes router, and Provider reconciliation.    |\n| [**`SPINEWORKSPACE_INFORMATION_ARCHITECTURE.md`**](SPINEWORKSPACE_INFORMATION_ARCHITECTURE.md) | **Workspace Information Architecture** — User experience, navigation hierarchies, domain lenses, and projection routing.                               |\n| [**`SPEC_AMENDMENTS_v1.md`**](SPEC_AMENDMENTS_v1.md)                                           | **Architectural Amendments** — Superseding corrections, naming unification, and legacy terminology deprecations.                                       |\n| [**`CANONICAL_PLATFORM_ARCHITECTURE.md`**](CANONICAL_PLATFORM_ARCHITECTURE.md)                 | **Platform Architecture Deep-Dive** — Multi-tenant isolation, Fortress storage, and context compilation.                                               |\n\n---\n\n## 2. Constitutions & Execution Governance\n\nFundamental invariant laws governing intelligence, actions, security, and runtime execution.\n\n| Document                                                                   | Focus Area                                                                                                              |\n| :------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------- |\n| [**`GOVERNED_EXECUTION_RUNTIME.md`**](GOVERNED_EXECUTION_RUNTIME.md)       | Closed-loop execution runtime, non-repudiation, provider receipt verification, and mutation lifecycles.                 |\n| [**`GOVERNANCE_CONSTITUTION.md`**](GOVERNANCE_CONSTITUTION.md)             | 3-tier risk classification, Rule R5 (_Confidence never grants authority_), and Human-in-the-Loop (HITL) approval gates. |\n| [**`TWIN_CONSTITUTION.md`**](TWIN_CONSTITUTION.md)                         | Cognitive co-worker behavior, OODA reasoning loop, signal sweep, and context grounding invariants.                      |\n| [**`TWIN_BEHAVIOR.md`**](TWIN_BEHAVIOR.md)                                 | Proactive assistance protocols, proposal synthesis, and noise-reduction heuristics.                                     |\n| [**`CAPABILITY_CONSTITUTION.md`**](CAPABILITY_CONSTITUTION.md)             | Capability Fabric invariants, tool invocation safety, and provider-agnostic capability abstraction.                     |\n| [**`CAPABILITY_FABRIC.md`**](CAPABILITY_FABRIC.md)                         | Dynamic capability registration, discovery, routing, and permission-aware resolution.                                   |\n| [**`CONNECTOR_CONSTITUTION.md`**](CONNECTOR_CONSTITUTION.md)               | Bi-directional connector contracts, sync modes (Webhook, Connector, Pipeline, Workflow).                                |\n| [**`PROJECTION_CONSTITUTION.md`**](PROJECTION_CONSTITUTION.md)             | Domain projection lenses, multi-view switchers (Table, Board, Calendar, Canvas), and Single Surface Law.                |\n| [**`RUNTIME_CONSTITUTION.md`**](RUNTIME_CONSTITUTION.md)                   | Platform execution constraints, session lifecycles, and tenant boundary preservation.                                   |\n| [**`CANONICAL_ENTITY_CONSTITUTION.md`**](CANONICAL_ENTITY_CONSTITUTION.md) | Canonical entity schemas, relationships, provenance, and lifecycle states.                                              |\n\n---\n\n## 3. Data Models, Schemas & SQL Contracts\n\nThe authoritative data contracts defining the Adaptive Spine and storage layers.\n\n| Document                                                                           | Schema Scope                                                                                             |\n| :--------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------- |\n| [**`CANONICAL_SPINE_SCHEMA.sql`**](CANONICAL_SPINE_SCHEMA.sql)                     | Comprehensive PostgreSQL / Neon DDL for entities, relationships, timeline events, signals, and evidence. |\n| [**`CANONICAL_SPINE_SCHEMA_FOUNDATION.md`**](CANONICAL_SPINE_SCHEMA_FOUNDATION.md) | Schema design principles, relational topology, foreign key constraints, and indexing strategy.           |\n| [**`CONTROL_PLANE_SCHEMA_AMENDMENTS.sql`**](CONTROL_PLANE_SCHEMA_AMENDMENTS.sql)   | Control plane schemas for tenant management, connector installations, and audit logging.                 |\n| [**`TENANT_D1_OPERATIONAL_SCHEMA.sql`**](TENANT_D1_OPERATIONAL_SCHEMA.sql)         | Cloudflare D1 / KV operational cache schema for high-throughput edge reads.                              |\n| [**`SPINE_ENTITY_TABLE_SCHEMA.md`**](SPINE_ENTITY_TABLE_SCHEMA.md)                 | Granular attribute dictionaries for accounts, opportunities, tickets, and tasks.                         |\n| [**`TENANT_LIFECYCLE_SCHEMA_REGISTER.md`**](TENANT_LIFECYCLE_SCHEMA_REGISTER.md)   | Provisioning, hydration, active, and decommissioning state transitions.                                  |\n| [**`ENTITY360_V2_MODEL.md`**](ENTITY360_V2_MODEL.md)                               | Multi-source entity consolidation contract and 360-degree context view specification.                    |\n\n---\n\n## 4. Ingress, Identity, MCP & Connector Mesh\n\nIdentity federation, Model Context Protocol (MCP) tooling, and external system connectivity.\n\n| Document                                                                                                                 | Subsystem Scope                                                                         |\n| :----------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------- |\n| [**`ONE_AUTH_WORKBENCH_PLATFORM_REFERENCE_ARCHITECTURE.md`**](ONE_AUTH_WORKBENCH_PLATFORM_REFERENCE_ARCHITECTURE.md)     | OneAuth session gateway, OAuth token broker, and zero-client-credential security model. |\n| [**`ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md`**](ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md)                                 | Host-aware session grants and projection hint propagation.                              |\n| [**`MCP_POOL_OPERATIONAL_SPINE_FABRIC_CONTRACT.md`**](MCP_POOL_OPERATIONAL_SPINE_FABRIC_CONTRACT.md)                     | Model Context Protocol tool pooling, discovery, and runtime invocation contracts.       |\n| [**`MCP_POOL_DEPLOYMENT_RING_ISOLATION_CONTRACT.md`**](MCP_POOL_DEPLOYMENT_RING_ISOLATION_CONTRACT.md)                   | Multi-environment ring isolation (Ring 0 Core, Ring 1 Internal, Ring 2 Marketplace).    |\n| [**`MCP_POOL_MULTI_ENVIRONMENT_STRATEGY.md`**](MCP_POOL_MULTI_ENVIRONMENT_STRATEGY.md)                                   | MCP server lifecycle management across dev, staging, and prod environments.             |\n| [**`IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md`**](IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md) | Third-party plugin SDK, manifest schemas, and capability verification.                  |\n| [**`CONNECTOR_RUNTIME_PROOF.md`**](CONNECTOR_RUNTIME_PROOF.md)                                                           | Provider connector execution verification and rate-limit handling.                      |\n\n---\n\n## 5. Deployment, Microfrontends & Repository Governance\n\nInfrastructure boundaries, deployment prerequisites, and repository hygiene.\n\n| Document                                                                                     | Focus Scope                                                                                |\n| :------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------- |\n| [**`DEPLOYMENT_PREREQUISITES.md`**](DEPLOYMENT_PREREQUISITES.md)                             | Mandatory pre-flight verification gates prior to staging and production deployment.        |\n| [**`CANONICAL_ECOSYSTEM_COVERAGE_COMPANION.md`**](CANONICAL_ECOSYSTEM_COVERAGE_COMPANION.md) | Complete implementation map across apps, packages, workers, and services.                  |\n| [**`application-boundaries.md`**](application-boundaries.md)                                 | Service boundary definitions between web, marketing, gateway, and background runtimes.     |\n| [**`HOST_AWARE_CONTINUITY_RUNTIME_SPEC.md`**](HOST_AWARE_CONTINUITY_RUNTIME_SPEC.md)         | Edge proxy routing, subdomain rewrites, and tenant hint handling.                          |\n| [**`MICROFRONTENDS.md`**](MICROFRONTENDS.md)                                                 | Composable microfrontend contracts (`@integratewise/auth-connectors-mfe`, `platform-mfe`). |\n| [**`CANONICAL_REPO_TOPOLOGY.md`**](CANONICAL_REPO_TOPOLOGY.md)                               | Monorepo structure, package boundaries, and dependency graphs.                             |\n| [**`REPOSITORY_BOUNDARY_AUDIT.md`**](REPOSITORY_BOUNDARY_AUDIT.md)                           | Clean boundary enforcement between product UI, marketing, and core library code.           |\n\n---\n\n## 6. Historical Lineage & Archival Records\n\n_The following documents are preserved for architectural lineage, decision history, and evolution context. When statements in these documents conflict with the Master Canonical Authorities, the Canonical Authorities take precedence._\n\n- [`integratewise-architecture-v2.0.md`](integratewise-architecture-v2.0.md), [`INTEGRATEWISE_ARCHITECTURE_v2.2.md`](INTEGRATEWISE_ARCHITECTURE_v2.2.md) — Earlier generation architectural syntheses.\n- [`locked-v1.md`](locked-v1.md), [`locked-v1.0.1.md`](locked-v1.0.1.md) — Version 1.0 specifications.\n- [`CONSOLIDATION_HANDOFF_LEDGER_2026-08-13.md`](CONSOLIDATION_HANDOFF_LEDGER_2026-08-13.md), [`DONOR_MIGRATION_REGISTER.md`](DONOR_MIGRATION_REGISTER.md) — Codebase migration ledgers.\n- [`CUSTOMER_ZERO_CONSTITUTION.md`](CUSTOMER_ZERO_CONSTITUTION.md), [`CUSTOMER_ZERO_DAILY_OPERATING_MANUAL.md`](CUSTOMER_ZERO_DAILY_OPERATING_MANUAL.md) — Customer Zero testbed operational guides.\n- [`source/`](source/), [`packaged/`](packaged/) — Extracted archive assets and raw notes.\n"}