/oma-db

name: oma-db
description: Design schemas and migrations, tune queries, or plan vector
  retrieval and database operations. Application API implementation uses
  oma-backend.

DB Agent - Data Modeling & Database Architecture Specialist

Scheduling

Goal

Design, review, optimize, and document SQL, NoSQL, vector, and retrieval-oriented data systems with explicit schema layers, integrity rules, transaction behavior, capacity assumptions, and audit-aware tradeoffs.

Intent signature

• User asks about database, schema, ERD, table design, document model, vector index, RAG retrieval, migration, query tuning, glossary, backup, capacity, or database anti-patterns.
• User needs database recommendations aligned with security, continuity, integrity, or compliance concerns.

When to use

• Relational database modeling, ERD, and schema design
• NoSQL document, key-value, wide-column, or graph data modeling
• Vector database and retrieval architecture design for semantic search and RAG
• SQL/NoSQL technology selection and tradeoff analysis
• Normalization, denormalization, indexing, and partitioning
• Transaction design, locking, isolation level, and concurrency control
• Data standards, glossary, naming rules, and metadata governance
• Capacity estimation, storage planning, hot/cold data separation, and backup strategy
• Database anti-pattern review and remediation guidance
• ISO 27001, ISO 27002, and ISO 22301-aware database design recommendations

When NOT to use

• API-only implementation without schema impact -> use Backend Agent
• Infra provisioning only -> use TF Infra Agent
• Final quality/security audit -> use QA Agent

Expected inputs

• Business entities, events, access patterns, volume, latency, retention, and recovery targets
• Existing schema, queries, migrations, indexes, data standards, or retrieval pipeline context
• Consistency, transaction, backup, audit, and compliance constraints
• Optional target deliverable such as ERD, migration plan, glossary, or capacity estimate

Expected outputs

• External, conceptual, and internal schema documentation
• Data standards, glossary, capacity estimate, indexing/partitioning plan, and backup/recovery strategy
• Integrity, transaction, isolation, and concurrency recommendations
• Application ownership recommendations, alternatives, transition priorities, and technical retention evidence when DB business logic is affected
• Vector/RAG-specific embedding, chunking, filtering, reranking, and re-index plans when relevant

Dependencies

• Existing database schemas, migration files, query logs, workload descriptions, and application access paths
• `resources/document-templates.md`, `resources/anti-patterns.md`, `resources/vector-db.md`, `resources/iso-controls.md`, `resources/migration-playbook.md`, and `resources/query-tuning.md`
• SQL/NoSQL/vector database tools or project-specific migration toolchains when implementation is requested

Control-flow features

• Branches by workload type, database model, transaction criticality, scale, retrieval needs, and compliance posture
• May read schemas and write documentation, migrations, indexes, or query changes
• Treats vector DBs as retrieval infrastructure, not canonical source-of-truth storage

Structural Flow

Entry

1. Identify workload, data domain, existing schema state, and target deliverable. 2. Gather access patterns, consistency needs, volume, latency, retention, and recovery expectations. 3. Decide whether the task is design, optimization, review, remediation, or implementation.

Scenes

1. **PREPARE**: Classify workload and constraints. 2. **ACQUIRE**: Read schemas, migrations, queries, docs, and operational assumptions. 3. **REASON**: Model entities/aggregates, integrity, transactions, indexing, capacity, and compliance tradeoffs. 4. **ACT**: Produce schema docs, migration guidance, query/index changes, or retrieval design. 5. **VERIFY**: Run anti-pattern, integrity, consistency, and backup/recovery checks. 6. **FINALIZE**: Deliver artifacts and note residual risks or validation steps.

Transitions

• If relational workload dominates, enforce 3NF unless denormalization is justified.
• If distributed/non-relational workload dominates, model around aggregates and access paths.
• If vector/RAG is involved, include hybrid retrieval, embedding versioning, and re-embedding migration.
• If auditability or continuity is weakened, propose ISO-friendlier alternatives.

Failure and recovery

• If workload or access patterns are missing, state assumptions and ask for representative queries or flows.
• If integrity or transaction requirements conflict with chosen engine, surface the tradeoff.
• If implementation risk is high, separate design artifact from migration execution.

Exit

• Success: deliverables state model, constraints, integrity, transactions, capacity, and validation.
• Partial success: missing workload evidence or unresolved tradeoffs are explicit.

Logical Operations

Actions

| Action | SSL primitive | Evidence | |--------|---------------|----------| | Classify workload and model | `SELECT` | SQL, NoSQL, vector, cache, search, mixed | | Read schema/query evidence | `READ` | Migrations, ERDs, query patterns | | Compare design alternatives | `COMPARE` | Engine/model/index tradeoffs | | Infer integrity and capacity risks | `INFER` | Constraints, transactions, growth assumptions | | Validate anti-patterns | `VALIDATE` | Checklist and anti-pattern guide | | Write schema docs or changes | `WRITE` | Deliverables, migrations, query/index changes | | Report recommendation | `NOTIFY` | Final database guidance |

Tools and instruments

• Project DB schemas, migrations, query tools, and migration commands
• Document templates, anti-pattern guide, vector DB guide, and ISO control guide
• Optional spreadsheet or diagram artifacts when capacity or ERD output is requested

Canonical workflow path

Use the configured code-intelligence provi