# MFENX Gate — organization runtime security and data flow

mfenx LLC · San Francisco, California

This is the current deployment record for the separately licensed organization runtime. The original technical-pack v1 ZIP and its security overview are retained unchanged as a historical SDK record, not as the current runtime configuration guide.

## Product and data flow

Gate is a local model-admission workflow and compact signed release-receipt format. The static browser verifier performs cryptographic checks with Web Crypto. The Python CLI verifies receipts, invokes the separately licensed CKODMK engine for supported ONNX evaluation, and inspects checkpoint integrity.

Model weights, evaluation samples and private signing keys are processed locally. They are not included in a compact receipt. A PCM package is different: it contains bound model and evaluation payloads and must be handled accordingly. Opening a public example downloads only that example. User-selected files are not uploaded, logged, stored in browser persistence or sent to an analytics service by the receipt instrument.

A receipt can disclose issuer name, artifact commitments, evaluation counts and policy identity. Share it deliberately. The optional organization runtime stores explicitly registered receipt metadata in the customer's own database; it is not an MFENX-hosted receipt-history service.

## Trust and assurance

The recipient selects a trusted P-256 SPKI public key independently. The verifier checks a strict versioned schema, canonical signature, content root, time validity, profile consistency and supplied artifact/policy commitments. Receipt authentication is an issuer attestation, not a proof of execution. Behavioral replay is separate. A recorded source identity does not establish an independently approved ancestry chain.

The release operator is responsible for signing-key custody, policy approval, local runtime trust, current trusted keys and system time. The deployment must load the exact bytes it checked. Current local verification does not query a revocation service. Apply rotation and expiry through the receiving trust policy.

## Execution profiles

ONNX issuance executes the approved CKODMK CPU classification contract and issues only on PASS. Inspection supports supported Safetensors/PyTorch inventory formats; receipt v1 Safetensors integrity issuance is single-file and does not attest to behavior. A finite evaluation does not establish behavior for untested inputs.

## Deployment controls

Pin packages, approved policy digests and runtime dependencies. Separate signing authority from model submissions. Do not make signing secrets available to untrusted pull requests. Retain evaluation evidence in access-controlled local storage and back up issuer material according to organization policy. Test updates and recovery before promotion.

The optional customer-operated organization runtime needs authenticated organization membership, TLS, durable storage, backup/recovery, independently trusted public entitlement keys and a valid signed license. It does not need Paddle credentials, an MFENX issuer private key or hosted billing routes. Receipt registration is transactional and idempotent. Organization policy and receipt records remain in the customer's environment.

MFENX's separate licensing service handles pseudonymous purchase-key and payment references; Paddle handles purchaser and payment information. Payment redirects do not establish entitlement. The licensing service reconciles current provider state before issuing a grant. Team and Business customers may run the optional one-shot renewal helper using protected customer-held recovery credentials; the organization runtime does not collect or host those credentials. Private air-gap grants retain disconnected delivery. Previously issued offline grants remain valid until their signed expiry; cancellation prevents new issuance, not instant offline revocation. Standalone receipt verification remains independent of subscription state.

The signed software-delivery manifest authenticates the exact organization-runtime archive and verifier and binds the separate public license issuer. It is neither a purchased entitlement nor a model-admission receipt. Installation instructions and independently enrolled publisher pins are at https://mfenx.com/docs/runtime/. The original technical-pack ZIP and component notices remain unchanged; this document describes the current separated deployment.

## Procurement artifacts

The exact delivered component package contains its applicable license and third-party notices. Paid internal use follows the published commercial terms at https://mfenx.com/terms/ and any applicable order. Deployment-specific data agreements, service commitments and requested tax forms are separate documents. This technical record is not a security certification, penetration-test report or warranty of defect-free operation.

Technical interfaces: https://mfenx.com/docs/
Free verifier: https://mfenx.com/verify/
Evidence: https://mfenx.com/evidence/