Relational Db

This is a Hermes-native relational-db workflow skill.

Why This Exists

relational-db exists because the database work itself had no owner: omh-backend owns schema_migration_plan/v1 for a service change, and an index question, a lock taken during deploy, or an N+1 finding was answered by a data, deploy, or interview lane with no lock model at all.

First Steps

• Ask for the engine, the version, and the table sizes before proposing any statement.
• For a migration, give every step its lock behaviour and its rollback before calling the plan ready.

Do Not Use When

• The request is a service or API change whose storage part is one section of the contract; use omh-backend, which owns schema_migration_plan/v1.
• The request is an end-to-end performance goal across the whole system rather than one database; use ulw-perf.
• The request is analysis of the data itself -- trends, metrics, a report; use omh-data-analysis.
• The request is watching a release roll out with its health signals and rollback criteria; use omh-deploy-and-monitor.