Signals

MySQL (mysql2)

The CMS's only database — deliberately kept as the single system of record instead of splitting state across multiple stores.

CloudPanel + Nginx + systemd

The VPS deployment stack — CMS and Alex OS run as separate systemd services behind Nginx on a single server.

pgvector

Optional Postgres extension Alex OS uses for content embeddings, with an automatic keyword-scoring fallback when it's not configured.

FastAPI

The framework Alex OS is built on — used for every route group (ask, surface, recommend, capture, synthesis, admin).

Anthropic API (Claude)

The LLM provider behind Alex OS's grounded answers, content generation, and content scoring.

Reindexing has to be triggered, not assumed

Alex OS only re-embeds content when the CMS calls its config-refresh route — a seed script that writes straight to MySQL has to call it manually.

pgvector is optional, not the system of record

Alex OS's semantic retrieval uses an optional Postgres/pgvector store — the CMS itself never left MySQL.

Content fields are data, not code

Because content_type_fields and content_items.fields_json are schemaless, adding a field to an existing type never touches existing records.

RAG best practices signal

What actually improves retrieval grounding and answer quality in practice.

Claude Code workflow signal

Agentic coding workflows that keep a human in the loop across phases.

NotebookLM workflow signal

Using NotebookLM to accelerate source-grounded research workflows.

New Sonnet 5