Public-safe database design packet

See the database review shape without publishing database material.

This checked-in synthetic example shows how table declarations, EF mappings, operation candidates, query references, route context, provenance, caps, gaps, and limitations travel together.

Public claim level: demo. Derived from database-design-review/1.0. The rows are synthetic public-safe projections shaped like the shipped output—not raw command output or evidence about a live system.

Packet identity

One public projection, two supported input modes.

Contractdatabase-design-review/1.0

Composition ruledatabase.design-review.packet.v1

Gap ruledatabase.design-review.gap.v1

Claim leveldemo for this public projection; nested packet claim level remains static-evidence.

Coveragepartial because the example preserves source, mode, and composition gaps.

Single index

Design evidence is useful even when graph paths are unavailable.

The single-index example retains PostgreSQL declarations, an EF table mapping, an application operation candidate, and a query reference. Its route-reference count is zero by contract.

table declarationpublic.orders · database.postgres.schema-migration.v1 · Tier2Structural · complete · repo-relative span · postgres-schema-migration/0.5.0

EF mappingstatus · database.ef.v1 · Tier1Semantic · complete · supporting fact ID retained · csharp-semantic/0.14.0

application operationinsert-candidate · database.operation.call-pattern.v1 · Tier1Semantic · candidate only

query referencepublic.orders · database.sql.shape.v1 · Tier3SyntaxOrTextual · exact static name match; query text and hash omitted

route coverage gapSingleIndexRoutePathUnavailable · database.design-review.gap.v1 · Tier4Unknown · route-reference count 0

Combined index

Existing static graph evidence can add bounded route context.

The combined-index example retains the same evidence families plus one synthetic route reference supported by packet, route, call, query, and operation rule IDs.

route referenceGET /orders/{id} · static path · exact table match · database.design-review.packet.v1 · supporting fact and edge IDs retained

path boundaryExisting graph evidence only; no runtime reachability, request traffic, authorization, deployment, provider selection, or user exercise is established.

remaining gapSourceCoverageReduced · source parsing or build coverage remains partial and cannot be upgraded by composition.

Evidence attachment

Proof identity survives the public projection.

Rule and tierEach evidence or gap row carries its rule ID and evidence tier.

Source identityPublic source label, full public commit SHA, and repo-relative file spans remain visible.

Extractor provenanceExtractor IDs and versions remain attached where the shipped packet provides them.

Supporting IDsAllowlisted synthetic fact, edge, and rule IDs preserve the shape of upstream support without publishing raw evidence.

CapsObject, evidence, route-reference, and gap omitted counts remain explicit, even when they are zero.

Public claim boundary

The packet supports design review, not a database conclusion.

It does not inspect a live database or catalog, execute SQL, queries, migrations, functions, jobs, or application code, or prove that a migration was applied.
It does not prove runtime provider or connection selection, generated SQL, search-path behavior, branch feasibility, runtime reachability, traffic, authorization, deployment, or user exercise.
It does not establish current or production schema, data correctness, compatibility, effective permissions, rollback, operational success, release approval, DBA approval, or that anything is safe to run.
It 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.

Keep the packet attached

Carry the example with its gaps and non-claims.

Public JSON packet Database design review Manager packet Proof paths for managers Packet examples Output artifacts Capabilities Limitations Rule catalog