Unclassified

Complete Deployment Analysis: Dec 14, 2025 - Jan 31, 2026

Tier C — Historical. This document is a point-in-time snapshot preserved for reference. For current architecture, see CANONICAL_PLATFORM_ARCHITECTURE.md.

Status: Code recovered. Deployment analysis complete.
Recovery Branch: recovery/integratewise-os-deployed
Current State: Build has 13 errors requiring fixes.

Executive Summary

The deployed IntegrateWise Operating System app was successfully recovered from the source repository and restored to apps/web. This was a Next.js 16 + React 19 application that existed separately during the Dec 14 - Jan 15 period, then was consolidated into this monorepo during the June 23-24 code excavation.

What Happened:

  1. Dec 14 - Jan 15: Deployed app lived in separate repo (integratewise/integratewise-ai-workspace@consolidation/monorepo-v11-features)
  2. Jun 23-24: Code consolidation into main repo (branch merges, v0 work, Replit handoff)
  3. Jun 25: Deployed app source recovered and restored to apps/web

Deployment Timeline & Phases

Phase 1: Initial Development (Pre-Dec 14)

Commits visible in history:

  • d204d65 - init (starting point)
  • aab0aa2 - chore: add vitest dependencies
  • 5262310 - feat(agent): implement MCP connector

Status: Foundation laid for backend services, MCP integration started.

Phase 2: Active Deployment Period (Dec 14 - Jan 15)

In separate repo (not directly visible here):

  • Built deployed Next.js landing page
  • Implemented 56+ route segments
  • Created 16 component directories
  • Built 25 lib utility directories
  • Deployed to Vercel (integratewize org)

Note: This period's commits are in integratewise-ai-workspace@consolidation/monorepo-v11-features, not in this repo's main branch.

Phase 3: Platform Services Build (Jan 15 - Jun 23)

Visible commits showing service implementation:

Service Infrastructure:

  • 1d0a611 - enhance auth, fix service bindings, add missing route
  • d2de377 - enable queues and update service bindings
  • d1091dc - platform verification & validation backend

Features Added:

  • ff2cd7f - add filter to dev script
  • 632622c - CF stack monitor + platform wiring
  • 73e9174 - Customer Zero Workspace component
  • e6ea7dc - reference images for CRM, dashboard, home, metrics, strategic
  • 82d4a51 - initial HTML and architecture docs

CI/Automation:

  • 2356d72 - update Babel dependencies
  • 47 (Merge #21) - code consolidation
  • 04a8a03 (Merge #20) - spec/v37-rc1-conflict-resolved

Phase 4: Code Excavation & Consolidation (Jun 23-24)

Major consolidation work:

Cleanup & Handoff:

  • cd065ff - platform delivery summary
  • fa7abcc - remove v0 experimental FE files
  • c539a3d - add public landing page + founder dashboard

Documentation Explosion:

  • db82920 - CONTRIBUTING guide
  • 2521210 - cleanup + memory/logging architecture
  • 3fb38a8 - cleanup summary
  • 49ac2f4 - landing page routing + GTM motion docs
  • 0928170 - complete tool connection flow
  • 02bd685 - ASCII architecture diagrams (7 flows)
  • e016a42 - documentation index
  • c9b2e4b - diagram verification (all 10 sections)
  • 7e90c7e - add vercel.json for Vite app
  • 3d40d66 - deployment fix explanation
  • d54ecc8 - handoff acceptance

Phase 5: Service Fixes & TS Cleanup (Jun 24)

13 TypeScript/Build Fixes:

  • 756c3a4 - outcome event ID generation (TS2339)
  • 7d2152d - drop unused EdgeEntity (TS6196)
  • 6eb5cb6 - D1 .results vs .data patterns (TS2304/TS2339)
  • 538123a - remove Supabase REST helpers (TS2339)
  • e868b8e - audit dbUrl parameter ordering (TS1016)
  • 5c08fbe - outcome event schema import (TS2305/TS6133)
  • 7fe9a0a - remove dead toEdgeEntity (TS6133/TS2353)
  • 8821b0e - remove queryDbProxy (TS6133/TS6192)
  • c58652b - Supabase props in verifyAuth (TS2353)
  • e81874d - prefix unused params (TS6133)
  • 7d746aa - agent-runtime errors
  • 6f206b9 - doctrine baseline update (unmasks errors)

Result: All TS errors in services resolved.

Main Merge:

  • c6288ab - Merge #25 (deployment-pipeline-issues)
  • Pulled 19 files from main
  • SERVICE_INVENTORY.md added (26 services)
  • PIPELINE_SERVICE_AUDIT.md added

Phase 6: App Recovery (Jun 25)

Recovery & Analysis:

  • 310d10a - final deployment ready checklist
  • c560b40 - merge summary
  • e838312 - RECOVERED DEPLOYED APP (current)

Deployment Analysis by Component

Backend Services (26 Total)

Tier 0: Ingress & Routing

  • Gateway (single ingress, 9 bindings)
  • Webhook-Ingress

Tier 1: Core Data

  • Tenants
  • Connector-Sync
  • Normalizer

Tier 2: Projection & Rendering

  • Pipeline
  • Twin-Orchestrator
  • L2
  • Intelligence
  • Knowledge
  • Govern
  • Store
  • Act

Tier 3: Capability Runtime

  • Hermes
  • Triage
  • Workflow
  • IW-Agent-Runtime
  • MCP-Connector

Tier 4: Supporting

  • Agent-Registry, Billing, Admin, Loader
  • Folder-Watcher, Continuity
  • Telemetry, Think, Connector

Status: All services documented, service bindings wired, D1 migration complete.

Frontend Application (Recovered)

Framework: Next.js 16.0.10 + React 19.2

Structure:

  • 56+ route segments in app/ directory
  • 16 component directories (ui, layout, forms, etc.)
  • 25 lib utility directories (auth, api, db, hooks, etc.)
  • Middleware: Auth guard
  • UI Framework: shadcn/ui

Current Status:

  • ✅ Structure recovered
  • ✅ All files restored
  • ⚠️ 13 build errors (missing dependencies)
  • ⚠️ Route conflicts (duplicate /today routes)
  • ⚠️ Missing shadcn/ui components (table, etc.)

Build Errors:

  1. Missing @/components/ui/table
  2. Missing @/components/ui/command
  3. Missing @/components/ui/dialog
  4. Missing @/components/ui/select
  5. Duplicate route resolution (/today vs /(personal)/today)
  6. AppShell component references
  7. (7 more component/import issues)

Key Events & Transitions

December 14 - January 15 (Deployment Period)

January 15 - June 23 (Service Build Phase)

  • Backend services built and deployed
  • Service bindings wired through gateway
  • D1 database schema created
  • Auth quarantine implemented
  • MCP connector operational

June 23-24 (Code Consolidation)

  • Branch consolidation across repos
  • v0 cleanup (experimental files removed)
  • Extensive documentation added
  • TypeScript errors fixed
  • Code excavation completed

June 25 (Recovery)

  • Deployed app source recovered from separate repo
  • Restored to apps/web in main repo
  • Created recovery/integratewise-os-deployed branch
  • 13 build errors identified
  • Ready for fixing and re-deployment

What Was Lost & How It Was Recovered

Loss Timeline

  1. Source Location: integratewise/integratewise-ai-workspace@consolidation/monorepo-v11-features
  2. Why Lost: During branch consolidation, the deployed code wasn't in the main GitHub repo history visible here
  3. Where It Was: In separate organization (integratewise) under integratewize account

Recovery Method

  1. Extracted from deployed URL metadata
  2. Located source branch in separate repo
  3. Copied entire apps/integrationwise-os/ directory
  4. Restored to apps/web/ in main repo
  5. Commit message documents the recovery
  6. Created recovery branch for tracking

Current State

  • ✅ Code is recovered and in repo
  • ✅ Recovery branch created: recovery/integratewise-os-deployed
  • ✅ Full structure intact: 56 routes, 16 components, 25 lib utils
  • ⚠️ Build needs fixes: 13 errors require component additions
  • ⚠️ Route conflicts: Need de-duplication

Next Steps

Immediate (Fix Build)

  1. Add missing shadcn/ui components via CLI
  2. Resolve route conflicts (consolidate duplicate /today routes)
  3. Verify all imports resolve
  4. Test build locally
  5. Push to production branch

Short Term (Verify Deployment)

  1. Deploy to Vercel via recovery/integratewise-os-deployed branch
  2. Test production URL
  3. Verify API connections to backend services
  4. Test auth flow

Medium Term (Integration)

  1. Wire frontend to real backend APIs
  2. Test M3 data integration paths
  3. Implement platform JWT/OAuth
  4. Set up monitoring & observability

Files & Locations

Recovery Branch:

git checkout recovery/integratewise-os-deployed

App Location:

apps/web/                              # Recovered Next.js app
apps/web/app/                          # 56+ route segments
apps/web/components/                   # 16 component dirs
apps/web/lib/                          # 25 utility dirs
apps/web.old/                          # Backup of old Vite app

Documentation:

DEPLOYMENT_ANALYSIS_FULL.md            # This file
MERGE_SUMMARY_FROM_MAIN.md            # Main branch merge details
SERVICE_INVENTORY.md                  # 26 services documented
PIPELINE_SERVICE_AUDIT.md             # Queue/binding architecture

Conclusion

The deployed IntegrateWise Operating System has been successfully recovered from branch consolidation. The Next.js application with 56 routes and comprehensive component library is now available in the recovery branch. With 13 fixable build errors identified, the path forward is clear: resolve dependencies, test, and re-deploy to production.

Status: RECOVERY SUCCESSFUL. READY FOR FIX & DEPLOY.