What problem does it solve? Teams need an independent acceptance gate that decides whether a finished data-model document is complete enough for an engineer to build the schema and write correct queries from it, without the reviewer silently rewriting the model or approving it on completeness alone. ## Core Features & Use Cases - Nine-condition review bar: Judges entities and keys, relationship cardinality and referential rules, access-pattern-justified indexes, normalization and paradigm choice, lifecycle and migration, diagram-to-table sync, privacy and scale, groundedness, and delta-scoped amends. - Paradigm-aware judgment: Evaluates relational, document, graph, wide-column, and key-value models in their own idiom instead of demanding normalization or foreign keys from NoSQL designs. - Machine-parseable verdict: Emits exactly VERDICT: approve or VERDICT: revise plus actionable findings naming the failed condition, location, and fix. - Use Case: After authoring a data model for a new orders service, run this reviewer before schema implementation; it flags a missing on-delete rule and an unjustified index, returning findings the author resolves in one revision pass. ## Quick Start Use reviewing-data-model on the finished data-model document at docs/specs/orders-data-model.md and return the verdict with findings.
