Category: data

In this page Overview Gregius Data captures operational records from every component — RAG, Search, Sync, Vectors, Connections, Models, Cron, and System — into a single centralized log. Each entry carries a severity level, a component classification, and a timestamp, with sensitive data masked automatically before storage. Site administrators can view, filter, export, and manage…

In this page Overview Gregius Data ships a full WP-CLI command surface under wp gg-data — eight command families covering sync, vectors, RAG answers, benchmarks, evaluation, listing, and logs. Every subcommand accepts a –format flag (table, json, or csv), producing deterministic output for scripts and CI/CD pipelines. Automation and scripting are a site operator’s most…

In this page Overview Gregius Data’s vector subsystem generates and manages semantic embeddings that power AI search and retrieval across your WordPress content. It supports three vector generation approaches — internal TF-IDF with vocabulary management, a stateless HashingTF method requiring no preparation step, and provider-backed API embeddings — each scoped to a data connection and…

In this page Overview The sync subsystem keeps your PostgreSQL database in sync with WordPress content — posts types, metadata, and taxonomies — in two complementary modes: Both modes route through the same content pipeline: HTML cleaning, MD5 hash change detection, chunking, and provider dispatch (PDO or PostgREST). Prerequisites How Sync Works A sync operation…

In this page Overview Gregius Data enhances WordPress search with PostgreSQL-powered retrieval. Full-text search, typo-tolerant trigram matching, and optional vector-based semantic search combine through a unified interface that integrates directly with the standard WordPress search experience. Prerequisites How to: Enable Enhanced Search Enhanced search replaces the default WordPress search with PostgreSQL-powered retrieval. Once enabled, all…

In this page Overview The Schema Management subsystem creates, verifies, versions, and upgrades the database contracts required by Gregius Data features — sync, search, and vectors. It handles both direct PostgreSQL connections and PostgREST/Supabase connections with provider-specific setup flows. Prerequisites How It Works The schema manager orchestrates lifecycle per connection, routing behavior based on the…

In this page Overview The Retry Queue subsystem recovers automatically from transient database sync failures. When a sync operation fails, the error is classified and, if recoverable, queued for automatic retry with exponential backoff. Items that exhaust all retry attempts move to a dead letter queue for operator review and manual recovery. Prerequisites How It…

In this page Overview Gregius Data’s RAG subsystem grounds every answer in your synchronized WordPress content. It orchestrates three sequential phases — retrieval, governance, and generation — returning answers with source attribution or explicit abstentions when acceptable evidence is unavailable. Prerequisites How RAG Works When a user submits a query, the RAG subsystem processes it…

In this page Overview The Gregius Data REST API exposes plugin capabilities through a versioned WordPress REST API surface at gg-data/v1. It surfaces CRUD and operational endpoints across settings, connections, schema, sync, vectors, search, RAG, models, prompts, logs, and interactions. Prerequisites API Fundamentals All routes are registered under the base namespace /wp-json/gg-data/v1. Routes are grouped…