Database design review

What database design, mappings, operations, and query relationships are visible in this repository?

TraceMap composes existing PostgreSQL schema and migration evidence, EF mappings, application database-operation candidates, query surfaces, and bounded route references into one review packet—with gaps and limitations kept beside every conclusion.

Public claim level: demo. This is a synthetic, public-safe illustration of the shipped database-design-review/1.0 output contract. It is not raw scan output, a live catalog inspection, or approval to change a database.

Manager question

Turn scattered repository clues into a bounded design conversation.

Declared designTables, columns, named constraints, indexes, enums, routines, snapshots, and migration operations recognized in checked-in PostgreSQL DDL.

Application mappingCompiler-resolved EF table and column mappings attached to compatible table evidence where the static identity match is bounded.

Operation candidatesRecognized EF, Dapper, ADO.NET, and Npgsql call shapes labeled as candidates—not executions or successful changes.

Query relationshipsSimple query/table correlation by exact, source-scoped static name match, without rendering query text or hashes.

Route contextExisting combined-graph paths can be retained as bounded references; they never establish runtime reachability or traffic.

Two supported inputs

The packet says exactly what its input can support.

Both modes reuse already-shipped evidence. Neither performs new SQL extraction, opens a database connection, or runs an application.

single index.sqlite

Repository design without graph paths

Includes compatible PostgreSQL schema and migration evidence, EF mappings, database-operation candidates, and query surfaces. Route references are zero and the packet records SingleIndexRoutePathUnavailable rather than inferring that no route exists.

combined combined.sqlite

Design evidence with bounded route context

Includes the same evidence families and may retain existing static route references when graph evidence reaches a matched query or operation surface. Missing paths remain gaps.

Review packet

Every row carries proof identity and its stopping point.

The deterministic Markdown and JSON outputs keep source identity, commit SHA, rule ID, tier, coverage, repo-relative span, extractor provenance, supporting IDs, caps, and limitations together.

database-design-review.mdHuman-readable sources, table groups, declarations, operations, query references, bounded route references, gaps, and limitations.

database-design-review.jsonStable 1.0 packet shape under rule database.design-review.packet.v1, with composition gaps under database.design-review.gap.v1.

coverageavailable, partial, or unavailable based on compatible static evidence, explicit gaps, and bounded truncation.

capsObject, evidence, route-reference, and gap limits stay visible through omitted counts and TruncatedByLimit evidence.

Questions this sharpens

Useful review prompts without pretending the packet knows production.

Schema ownershipWhich checked-in declarations and migrations describe this table, and which parser gaps still need a database owner?

Model alignmentWhich EF mappings correlate to the static table identity, and which conventions or runtime model behavior remain unavailable?

Change surfaceWhich application call sites are candidates for reads, writes, saves, transactions, or direct commands?

Entry contextWhich existing route paths reach the static query or operation evidence, and where did path evidence stop?

Coverage decisionWhich gaps require source review, migration tooling, DBA validation, tests, or runtime observability before a decision?

Non-claims

A design-review packet is evidence for questions, not database authority.

TraceMap does not inspect a live database or catalog, execute SQL, queries, migrations, functions, jobs, or application code, or establish that a migration was applied.
Static matches do not prove runtime provider or connection selection, search-path behavior, generated SQL, branch feasibility, runtime reachability, traffic, authorization, deployment, or user exercise.
The packet does not establish the current or production schema, data correctness, compatibility, effective permissions, rollback, operational success, release approval, DBA approval, or that anything is safe to run.
The public example contains no raw SQL, source snippets or snippet hashes, credentials, connection strings, scheduled command bodies, local paths, private infrastructure identities, raw command output, raw SQLite, or arbitrary fact properties.
The core scanner and reducer use no LLM calls, embeddings, vector databases, or prompt-based classification.

Continue the proof path

Inspect the example, then keep its boundaries attached.

Database design proof packet Manager packet Proof paths for managers Packet examples Output artifacts Capabilities Evidence tiers Limitations Rule catalog