Story: Consolidation — absorb pal-e-docs into Rails monolith

story-paldocs-consolidation User Story

active user-story

Project

story: Consolidation — absorb pal-e-docs into Rails monolith

Role

Platform Owner (Lucas)

Key

consolidation

Want

As the platform owner, I want paldocs (Rails 8) to absorb pal-e-docs (FastAPI) — owning the database schema, API endpoints, and embedding pipeline

So That

So that the knowledge layer runs as a single Rails monolith instead of two apps sharing a database

Acceptance Criteria

Rails owns the paledocs PostgreSQL schema via ActiveRecord migrations (structure.sql format)
All pal-e-docs REST endpoints are served by Rails API controllers under /api/
Embedding pipeline runs as Solid Queue background jobs instead of Python workers
pal-e-mcp (or successor) calls Rails endpoints instead of FastAPI
pal-e-docs (FastAPI) can be shut down with no loss of functionality

Success Metric

pal-e-docs FastAPI service is decommissioned; all MCP tools and UI features operate against the Rails monolith with no regressions.

arch-rails-db — schema ownership and pgvector
arch-rails-api — MCP-compatible REST surface
arch-rails-jobs — Solid Queue embedding pipeline

project-paldocs — parent project page
board-paldocs — project board