Files
resolutionflow/backend
Michael Chihlas b49772f1a1 feat(models): Phase 1 SQLAlchemy models — SessionFact, SessionSuggestedFix, DraftTemplate, AccountSettings
Backs the schema added in 210d310 with SQLAlchemy 2.0 models.

- SessionFact: "What we know" facts with polymorphic source_ref pointing
  at task-lane item UUIDs inside ai_sessions.pending_task_lane (not a FK
  per Section 4.2).
- SessionSuggestedFix: AI-proposed resolutions with supersession tracking
  and the full user_decision state machine.
- DraftTemplate: post-resolve templatization queue with promotion to
  script_templates.
- AccountSettings: per-account JSONB preferences grab-bag with async
  classmethod helpers — get_setting(db, account_id, key, default) reads
  without creating, set_setting(db, account_id, key, value) upserts via
  Postgres ON CONFLICT + jsonb `||` merge so existing keys are preserved.
  Lazy row creation matches the Phase 1 design.

Column additions on existing models to mirror the migration:
- AISession: resolution_note_* / escalation_package_* / state_version
  (the preview-cache-invalidation counter consumed by Phase 3).
- ScriptTemplate: source_session_id / source_user_id / source_ticket_ref
  (provenance for templates promoted from DraftTemplate).

All four new models registered in app.models.__init__ and __all__.
TYPE_CHECKING-guarded relationship imports throughout, matching the
repo's existing model style.

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

Troubleshooting Decision Tree - Backend API

FastAPI backend for the Troubleshooting Decision Tree application.

Quick Start

1. Set up Python environment

cd backend
python -m venv venv

# Windows
venv\Scripts\activate

# macOS/Linux
source venv/bin/activate

pip install -r requirements.txt

2. Start PostgreSQL database

Using Docker:

docker-compose up -d

Or install PostgreSQL locally and create a database:

CREATE DATABASE decision_tree;

3. Configure environment

Copy the example env file and update as needed:

cp .env.example .env

4. Run database migrations

alembic upgrade head

5. Start the server

uvicorn app.main:app --reload --host 0.0.0.0 --port 8000

The API will be available at:

API Endpoints

Authentication

  • POST /api/v1/auth/register - Register new user
  • POST /api/v1/auth/login - Login (form data)
  • POST /api/v1/auth/login/json - Login (JSON body)
  • POST /api/v1/auth/refresh - Refresh token
  • GET /api/v1/auth/me - Get current user
  • POST /api/v1/auth/logout - Logout

Trees

  • GET /api/v1/trees - List all trees
  • GET /api/v1/trees/categories - List categories
  • GET /api/v1/trees/search?q=query - Search trees
  • GET /api/v1/trees/{id} - Get specific tree
  • POST /api/v1/trees - Create tree (engineer/admin)
  • PUT /api/v1/trees/{id} - Update tree (engineer/admin)
  • DELETE /api/v1/trees/{id} - Delete tree (admin)

Sessions

  • GET /api/v1/sessions - List user's sessions
  • GET /api/v1/sessions/{id} - Get specific session
  • POST /api/v1/sessions - Start new session
  • PUT /api/v1/sessions/{id} - Update session
  • POST /api/v1/sessions/{id}/complete - Complete session
  • POST /api/v1/sessions/{id}/export - Export session

Development

Create new migration

alembic revision --autogenerate -m "description"

Run migrations

alembic upgrade head

Rollback migration

alembic downgrade -1

Project Structure

backend/
├── alembic/              # Database migrations
│   └── versions/
├── app/
│   ├── api/
│   │   ├── endpoints/    # API route handlers
│   │   ├── deps.py       # Dependencies (auth, etc.)
│   │   └── router.py     # Main router
│   ├── core/
│   │   ├── config.py     # Settings
│   │   ├── database.py   # DB connection
│   │   └── security.py   # JWT, password hashing
│   ├── models/           # SQLAlchemy models
│   ├── schemas/          # Pydantic schemas
│   └── main.py           # FastAPI app
├── tests/
├── alembic.ini
├── docker-compose.yml
├── requirements.txt
└── README.md