Michael Chihlas 92fadfb90a docs(flowpilot-migration): integrate Codex plan review + Phase 0 audit findings
Significant rewrite of FLOWPILOT-MIGRATION.md after post-Codex plan review
and the Phase 0 in-flight audit. Archives the pre-rewrite version as
FLOWPILOT-MIGRATION-v1.md and keeps the Codex review under
CODEX-FlowAssist-Migration-PLAN.md for traceability.

Substantive changes that affect implementation:

- Section 0.1 adds a spec-drift note listing corrections integrated into
  this revision (API namespace, task-lane item UUIDs, account_settings
  creation, missing /tickets/ai-parse endpoint).
- Section 2 adds "Task lane item ID" terminology — stable UUID assigned
  to items inside ai_sessions.pending_task_lane so session_facts.source_ref
  has something reliable to point to.
- Section 4.1 adds ai_sessions.state_version (INTEGER NOT NULL DEFAULT 0)
  and escalation_package_external_id. state_version drives preview cache
  invalidation; incremented atomically on writes to facts / suggested
  fixes / script_generations.
- Section 4.6 creates account_settings as a new table with JSONB
  preferences column, lazy row creation, and a promotion rule for when a
  setting should graduate to a typed column.
- Section 5 namespaces all session-scoped routes under
  /api/v1/ai-sessions/{id}/... to match the existing codebase pattern.
- Section 5.5 documents the preview caching strategy (state_version
  keyed, 500ms client debounce, Redis planned).
- Section 6.6 adds per-service MCP capability flags alongside the model
  tier flags.
- Section 7.1 makes the /assistant -> /pilot redirect include the
  session-deep-link path and preserve the session ID.
- Section 8.2 adds supersession semantics for [SUGGEST_FIX] markers.
- Section 9 Phase 1 now explicitly includes account_settings and
  state_version; Phase 3 uses state_version-keyed caching; Phase 5
  mentions MCP inheritance via chat_call_cached wrapper.
- Section 11 adds a dedicated test plan (migrations, backend, frontend,
  manual QA).
- Section 14 captures the eight planning decisions made during the
  Phase 0 conversation so they are traceable.

No code changes in this commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-17 17:05:04 +00:00

ResolutionFlow

Stop writing ticket notes. Start generating them.

ResolutionFlow is an AI-powered troubleshooting platform for MSP professionals. Engineers follow guided flows while an AI copilot assists — and documentation writes itself as a byproduct of the work.

Production: resolutionflow.com


Quick Start

# Prerequisites: Docker, Python 3.11+, Node.js 20+

# Start PostgreSQL
docker start patherly_postgres

# Backend
cd backend
source venv/bin/activate
pip install -r requirements.txt
alembic upgrade head
uvicorn app.main:app --reload

# Frontend (separate terminal)
cd frontend
npm install
npm run dev

See DEV-ENV.md for full environment setup (devserver, Docker, CORS).


Features

FlowPilot AI Copilot

Like having a senior engineer on every call. FlowPilot guides troubleshooting decisions, suggests next steps with context-aware intelligence, and automatically captures documentation as a byproduct of the session.

  • Confidence-tiered model routing (fast responses for simple steps, deeper reasoning for complex decisions)
  • AI-generated ticket summaries and session documentation
  • Standalone assistant chat with RAG for open-ended troubleshooting
  • Knowledge Flywheel: AI analyzes completed sessions and proposes new flows automatically

Guided Flows

  • Troubleshooting Flows — Decision trees with branching paths for diagnosing issues
  • Procedural Flows (Projects) — Step-by-step checklists for onboarding, migrations, deployments
  • Maintenance Flows — Scheduled recurring tasks with batch execution across multiple targets
  • Visual Flow Editor with drag-and-drop canvas, undo/redo, markdown support
  • AI Flow Builder — describe what you need, get a complete flow generated

Auto-Documentation

Every session generates timestamped, detailed notes formatted for your PSA. Engineers never write another ticket note.

  • Export to Markdown, plain text, or HTML
  • Sensitive data redaction
  • One-click push to ConnectWise PSA tickets

ConnectWise PSA Integration

  • Post session documentation directly to ConnectWise tickets as internal notes
  • Pull ticket details and client context into FlowPilot sessions
  • Member mapping between ResolutionFlow and ConnectWise users
  • Credentials encrypted at rest (Fernet), stored per-team

Team & Knowledge Management

  • Role-based access (super_admin, team_admin, engineer, viewer)
  • Shared flow library with categories, tags, folders, full-text search
  • Step Library — reusable troubleshooting steps with ratings and reviews
  • Session sharing via link (authenticated and public views)
  • Escalation workflow with AI-enhanced briefing packages
  • Flow proposals from AI analysis (review queue for team leads)

Tech Stack

Layer Technology
Frontend React 19, TypeScript, Vite, Tailwind CSS v4
State Zustand (immer + zundo for undo/redo)
Routing React Router v7
Canvas @xyflow/react (React Flow) + dagre
Backend Python FastAPI, async SQLAlchemy 2.0 + asyncpg
Database PostgreSQL 16
Migrations Alembic (75+ migrations)
Auth JWT (python-jose) + bcrypt, refresh token rotation
AI Anthropic Claude API (tiered model routing)
Embeddings Voyage AI (semantic search)
Scheduling APScheduler 3.x (async)
Analytics PostHog
Hosting Railway (auto-deploy on push to main)

Project Structure

patherly/
├── backend/
│   ├── app/
│   │   ├── main.py                 # FastAPI entry point
│   │   ├── api/endpoints/          # Route handlers (35+ endpoints)
│   │   ├── core/                   # Config, database, permissions, security
│   │   ├── models/                 # SQLAlchemy models
│   │   ├── schemas/                # Pydantic schemas
│   │   └── services/psa/           # PSA provider abstraction layer
│   ├── alembic/                    # Database migrations
│   └── tests/                      # Integration tests (100+)
├── frontend/
│   ├── src/
│   │   ├── components/             # UI components by domain
│   │   ├── pages/                  # Page components
│   │   ├── store/                  # Zustand stores
│   │   └── types/                  # TypeScript interfaces
├── docs/                           # Design docs, plans, ConnectWise reference
├── brand-assets/                   # SVGs, brand guide
├── CLAUDE.md                       # AI assistant project context
├── CURRENT-STATE.md                # Detailed feature status
└── CHANGELOG.md                    # Release history

Running Tests

# Backend integration tests
cd backend
pytest --override-ini="addopts="

# Frontend build (stricter than tsc --noEmit)
cd frontend
npm run build

Documentation

Document Purpose
CLAUDE.md Full project context for AI-assisted development
CURRENT-STATE.md Detailed feature status
03-DEVELOPMENT-ROADMAP.md Development roadmap
UI-DESIGN-SYSTEM.md Design system (Slate & Ice)
DEV-ENV.md Development environment setup
CHANGELOG.md Release history

License

Proprietary. All rights reserved.

Description
Troubleshooting decision tree application for MSP engineers - automatically generates professional documentation from guided diagnostic workflows
Readme 16 MiB
Languages
Python 54.7%
TypeScript 43.5%
HTML 1.1%
CSS 0.6%