Data Pipelines

This is a Hermes-native data-pipelines workflow skill.

Why This Exists

data-pipelines exists because pipeline work had no owner: omh-backend owns a service's schema migration, omh-data-analysis analyzes data it is handed, and omh-relational-db owns a database's locks and indexes, while a backfill that duplicated events or a schema change with unknown readers reached memory and event lanes with no idempotency contract or replay bound at all.

First Steps

• Ask what makes a row unique at the sink before planning any rerun.
• Bound the window and the targets before ordering any replay or backfill step.

Do Not Use When

• The ask is a service's own database migration, API, or queue design; use omh-backend.
• The ask is analyzing, charting, or summarizing a dataset that was handed over; use omh-data-analysis.
• The ask is a slow query, an index, or DDL locking a live table; use omh-relational-db.
• The ask is remembering or syncing what the assistant knows about the user; use omh-memory-sync.