deepseek-ai/DeepSeek-V3

text-generationtransformersdeepseek685B params · updated Mar 2025

Mainframe serving

Can a COBOL transaction program call this checkpoint, and under which transport? The model returns evidence; the host keeps the decision.

Export status

Exportable with care

Custom remote code; needs operator registration

Recommended pattern

Pattern 03

Message queue

Latency class

Async

ONNX artifact

Not measured

measured once the harness posts results

Screening note

Scored in batch by a GPU consumer pool; the batch window, not the model, sets the deadline.

685B parameters cannot answer inside a transaction; score asynchronously

Internal network only; durable queue inside the perimeter

Custom modelling code (custom_code / auto_map) — operators may need registration

osai-screening/1.0.0 · verdict f5a2a71154224dce…

Serving controlskill switch offshadow onconfidence floor 0.85GET /serving-status

Promotion gates

Gate	What it checks	State
Structural check	Graph loads; node inputs, outputs and shapes resolve	Not run
Numerical parity	Same inputs agree with the source framework within 1e-4	Not run
Eight-bit quantisation	INT8 weights with parity re-run afterwards	Not run
Shadow cycle	Full cycle scored against live traffic with no influence on outcomes	Not run

Interface contract

The copybook is generated, versioned and never hand-edited on either side. Entry point SCORE_DEEPSEEK_V3.

Generated copybookmodel record · contract

      * GENERATED BY osai-copybook-gen/1.0.0 — DO NOT EDIT (STANDARD S2)
      * COPYBOOK FOR deepseek-ai/DeepSeek-V3
      * REVISION e815299b0bcb  PATTERN 03  ENTRY SCORE_DEEPSEEK_V3
       01  SCORE-DEEPSEEK-V3-REQUEST.
           05  REQ-RECORD-ID          PIC X(12).
           05  REQ-TEXT-LEN           PIC S9(4) COMP-5.
           05  REQ-TEXT               PIC X(4000).
       01  SCORE-DEEPSEEK-V3-RESPONSE.
           05  RESP-SCORE             COMP-1.
           05  RESP-CONFIDENCE        COMP-1.
           05  RESP-LABEL             PIC X(16).
           05  RESP-MODEL-VERSION     PIC X(16).
           05  RESP-STATUS            PIC S9(4) COMP-5.

SCORE-DEEPSEEK-V3-REQUEST / OsaiRequest4014 bytes

COBOL	C	Kind	Offset	Bytes	Note
REQ-RECORD-ID	record_id	alnum(12)	0	12	caller correlation key, logged with the inference
REQ-TEXT-LEN	text_len	binary16	12	2	bytes used in REQ-TEXT
REQ-TEXT	text	alnum(4000)	14	4000	de-identified text; tokenized inside the graph

SCORE-DEEPSEEK-V3-RESPONSE / OsaiResponse42 bytes

COBOL	C	Kind	Offset	Bytes	Note
RESP-SCORE	score	float32	0	4	model output; evidence, not a decision
RESP-CONFIDENCE	confidence	float32	4	4	compared against the confidence floor by the host
RESP-LABEL	label	alnum(16)	8	16	e.g. REVIEW or APPROVED — never DENY
RESP-MODEL-VERSION	model_version	alnum(16)	24	16	revision that produced the score (standard S4)
RESP-STATUS	status	binary16	40	2	0 scored · 4 below floor · 8 transport or runtime failure — 4 and 8 fall through to host rules

CLAIMPROC.cob — the callergenerated by the screening service

       IDENTIFICATION DIVISION.
       PROGRAM-ID. OSAICALL.
       DATA DIVISION.
       WORKING-STORAGE SECTION.
           COPY OSAICPY.
       77  CONFIDENCE-FLOOR     COMP-1 VALUE 0.85.
       PROCEDURE DIVISION.
           CALL "MQPUT" USING HCONN, HOBJ, MD, PMO,
             LENGTH OF SCORE-DEEPSEEK-V3-REQUEST, SCORE-DEEPSEEK-V3-REQUEST, COMPCODE, REASON
           IF COMPCODE NOT = 0
             PERFORM LOG-MQ-FAILURE
           END-IF
      *    PASS 2 READS SCORED ROWS AND APPLIES THE SAME EVALUATE
           GOBACK.

The C-ABI wrapper is on the Usage tab under “C bridge”. Test the bridge on a workstation with GnuCOBOL before it reaches an LPAR — struct packing and numeric conversion are what actually break, and they are identical on both targets.

Standards this deployment inherits

Download ML-BOM

S1Models ship as ONNX artifacts. No ML framework runtime is installed on z/OS.

S2The copybook is the interface contract — generated, versioned, never hand-edited on either side.

S3Latency class selects the pattern. Team preference and vendor enthusiasm do not.

S4Every inference is logged with the record state and model version that produced it.

S5PHI leaves the platform only tokenized, over mTLS, to an endpoint under an executed BAA.

S6A model influences payment only after a full shadow cycle and with a tested fallback path.