Unclassified

IntegrateWise & Spine Workspace — Architecture Documentation Index

Status: Canonical Authority Index
Version: v3.0.0-Canonical
Authority Hierarchy: SYSTEM_ARCHITECTURE_CANONICAL.md → INTEGRATEWISE_ARCHITECTURE.md → Subsystem Constitutions

1. Master Canonical Authorities

These documents define the definitive architecture, category positioning, information hierarchy, and execution models across the entire platform.

DocumentFocus & Authority Scope
SYSTEM_ARCHITECTURE_CANONICAL.mdPrimary Platform Authority (v3.0.0) — Complete 6-Layer Stack, 12-Step Loop, Single Context Law, 18 Projections, Governance & Ingress Architecture.
INTEGRATEWISE_CANONICAL_REFERENCE.mdCanonical Reference & Doctrine — 5-Layer Stack, 8 Spine Domains, 6 Storage Substrates, Universal Write Path, and 5-Zone UI grammar.
INTEGRATEWISE_USER_JOURNEY.mdUser Journey & Activation Blueprint — 8 Journey Stages (Enter → Loop) and 7 Activation Readiness Gates.
INTEGRATEWISE_ARCHITECTURE.mdCore Subsystem Specification — Technical architecture, Adaptive Spine substrate, Capability Fabric, Hermes router, and Provider reconciliation.
SPINEWORKSPACE_INFORMATION_ARCHITECTURE.mdWorkspace Information Architecture — User experience, navigation hierarchies, domain lenses, and projection routing.
SPEC_AMENDMENTS_v1.mdArchitectural Amendments — Superseding corrections, naming unification, and legacy terminology deprecations.
CANONICAL_PLATFORM_ARCHITECTURE.mdPlatform Architecture Deep-Dive — Multi-tenant isolation, Fortress storage, and context compilation.

2. Constitutions & Execution Governance

Fundamental invariant laws governing intelligence, actions, security, and runtime execution.

DocumentFocus Area
GOVERNED_EXECUTION_RUNTIME.mdClosed-loop execution runtime, non-repudiation, provider receipt verification, and mutation lifecycles.
GOVERNANCE_CONSTITUTION.md3-tier risk classification, Rule R5 (Confidence never grants authority), and Human-in-the-Loop (HITL) approval gates.
TWIN_CONSTITUTION.mdCognitive co-worker behavior, OODA reasoning loop, signal sweep, and context grounding invariants.
TWIN_BEHAVIOR.mdProactive assistance protocols, proposal synthesis, and noise-reduction heuristics.
CAPABILITY_CONSTITUTION.mdCapability Fabric invariants, tool invocation safety, and provider-agnostic capability abstraction.
CAPABILITY_FABRIC.mdDynamic capability registration, discovery, routing, and permission-aware resolution.
CONNECTOR_CONSTITUTION.mdBi-directional connector contracts, sync modes (Webhook, Connector, Pipeline, Workflow).
PROJECTION_CONSTITUTION.mdDomain projection lenses, multi-view switchers (Table, Board, Calendar, Canvas), and Single Surface Law.
RUNTIME_CONSTITUTION.mdPlatform execution constraints, session lifecycles, and tenant boundary preservation.
CANONICAL_ENTITY_CONSTITUTION.mdCanonical entity schemas, relationships, provenance, and lifecycle states.

3. Data Models, Schemas & SQL Contracts

The authoritative data contracts defining the Adaptive Spine and storage layers.

DocumentSchema Scope
CANONICAL_SPINE_SCHEMA.sqlComprehensive PostgreSQL / Neon DDL for entities, relationships, timeline events, signals, and evidence.
CANONICAL_SPINE_SCHEMA_FOUNDATION.mdSchema design principles, relational topology, foreign key constraints, and indexing strategy.
CONTROL_PLANE_SCHEMA_AMENDMENTS.sqlControl plane schemas for tenant management, connector installations, and audit logging.
TENANT_D1_OPERATIONAL_SCHEMA.sqlCloudflare D1 / KV operational cache schema for high-throughput edge reads.
SPINE_ENTITY_TABLE_SCHEMA.mdGranular attribute dictionaries for accounts, opportunities, tickets, and tasks.
TENANT_LIFECYCLE_SCHEMA_REGISTER.mdProvisioning, hydration, active, and decommissioning state transitions.
ENTITY360_V2_MODEL.mdMulti-source entity consolidation contract and 360-degree context view specification.

4. Ingress, Identity, MCP & Connector Mesh

Identity federation, Model Context Protocol (MCP) tooling, and external system connectivity.

DocumentSubsystem Scope
ONE_AUTH_WORKBENCH_PLATFORM_REFERENCE_ARCHITECTURE.mdOneAuth session gateway, OAuth token broker, and zero-client-credential security model.
ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.mdHost-aware session grants and projection hint propagation.
MCP_POOL_OPERATIONAL_SPINE_FABRIC_CONTRACT.mdModel Context Protocol tool pooling, discovery, and runtime invocation contracts.
MCP_POOL_DEPLOYMENT_RING_ISOLATION_CONTRACT.mdMulti-environment ring isolation (Ring 0 Core, Ring 1 Internal, Ring 2 Marketplace).
MCP_POOL_MULTI_ENVIRONMENT_STRATEGY.mdMCP server lifecycle management across dev, staging, and prod environments.
IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.mdThird-party plugin SDK, manifest schemas, and capability verification.
CONNECTOR_RUNTIME_PROOF.mdProvider connector execution verification and rate-limit handling.

5. Deployment, Microfrontends & Repository Governance

Infrastructure boundaries, deployment prerequisites, and repository hygiene.

DocumentFocus Scope
DEPLOYMENT_PREREQUISITES.mdMandatory pre-flight verification gates prior to staging and production deployment.
CANONICAL_ECOSYSTEM_COVERAGE_COMPANION.mdComplete implementation map across apps, packages, workers, and services.
application-boundaries.mdService boundary definitions between web, marketing, gateway, and background runtimes.
HOST_AWARE_CONTINUITY_RUNTIME_SPEC.mdEdge proxy routing, subdomain rewrites, and tenant hint handling.
MICROFRONTENDS.mdComposable microfrontend contracts (@integratewise/auth-connectors-mfe, platform-mfe).
CANONICAL_REPO_TOPOLOGY.mdMonorepo structure, package boundaries, and dependency graphs.
REPOSITORY_BOUNDARY_AUDIT.mdClean boundary enforcement between product UI, marketing, and core library code.

6. Historical Lineage & Archival Records

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.