@machynx/data-db

Machynx data-plane Prisma schema and generated client package.

Installation

npm install @machynx/data-db @prisma/adapter-pg

Usage

import 'dotenv/config';
import { PrismaClient } from '@machynx/data-db';
import { PrismaPg } from '@prisma/adapter-pg';

const prisma = new PrismaClient({
  adapter: new PrismaPg({
    connectionString: process.env.DATA_DATABASE_URL!,
  }),
});

const users = await prisma.coreUser.findMany();

The Prisma CLI reads DATA_DATABASE_URL from prisma.config.ts. Use the same value for the runtime adapter connection string.

Electrical Telemetry Contract

Generic telemetry rows and meter-register models live under the modular Prisma schema. The source-to-canonical electrical meaning boundary is defined in:

• prisma/schema/telemetry/electrical_metric_contract.prisma
• docs/2026-08-02-epm70-cross-repo-alignment.md

ElectricalMetricContract distinguishes electrical semantic, phase/topology, direction, cumulative/monotonic behavior, register lineage, and verification status. MeterPipelineValidationEvidence keeps simulator, physical serial, physical end-to-end, ACK reconciliation, and replay verification as separate claims.

The initial EPM70 catalog is intentionally not marked analytics-ready. Physical EM -> OSS -> BE -> DATA_DB persistence and ACK reconciliation must be proven before the relevant rows become END_TO_END_VERIFIED.