Program: peer TypeSpec/JSON Schema authorities and Diesel/SeaORM parity #19

Governing architecture

TypeSpec and JSON Schema/OpenAPI are independent top-level contract authorities:

TypeSpec -> SQL, Protobuf, gRPC, wire clients
JSON Schema/OpenAPI -> SQL, interfaces/types, validators, write clients

Their SQL candidates are materialized and compared through DPM catalogs. Their canonical type/operation manifests are compared separately. Diesel and SeaORM then independently project the agreed candidate database and cross-check manifests plus shared read/write fixtures.

Non-negotiable discrepancy rule

Missing artifacts, invalid artifacts, generator failures, unsupported constructs, SQL catalog differences, type differences, ORM differences, or fixture-result differences must produce a machine-readable pause decision. Automation must never elect a preferred source or ORM, copy one output over another, apply a migration, or publish clients while paused.

Workstreams

• TypeSpec custom SQL emitter plus pinned Protobuf/gRPC/wire-client generation.
• JSON Schema/OpenAPI SQL, interface/type, validator, and write-client generation.
• DPM catalog parity for both PostgreSQL and CockroachDB candidates.
• Canonical cross-language type and operation manifests.
• Diesel and SeaORM projection adapters and query/effect fixtures.
• Immutable discrepancy reports, review records, and clean-regeneration protocol.
• E2E discrepancy injection across supported engine/tool versions.
• Linear project/doc synchronization and release dashboarding.

Initial implementation branches

• declarative-postgres-migrate.rs:audit/peer-authority-parity-gates
• declmig-interfaces:audit/peer-contract-authorities
• declmig-orm-core:audit/diesel-seaorm-parity
• declmig-lib-core:audit/peer-persistence-authorities

This issue is the organization-level tracker. Repository issues should own executable implementation and acceptance evidence.