# Private inference — deployment acceptance and release record

Status: UNFILLED TEMPLATE. Not a test result, certification, signed agreement, or completed customer deployment.
Version: September 9, 2026.
Offer: proposed private workflow implementation, one model, one environment, one existing application's synchronous caller path.
Pricing and contract terms live in the signed scope. This document does not grant access or accept a release.

## 1. Scope and owners

- Project and release ID:
- Model / task:
- Application caller:
- Environment / cloud account / region / host:
- Infrastructure owner:
- Application owner:
- Delivery engineer and approved participants:
- Nominated operator after handover:
- Deadline, review window, and prerequisites:
- Included path:
- Excluded systems and paths:
- Out-of-scope changes and approval owner:

## 2. Release identity

- Model publisher, repository, immutable revision, and applicable license:
- Approved model files, sizes, and hashes:
- Runtime, packages, container image digest, operating system, architecture, drivers:
- Deployment / caller source revisions:
- Configuration and dependency inventory:
- Hardware / GPU / memory / storage:
- Secrets references (no secret values):
- Permitted download, preprocessing, logging, telemetry, and support destinations:

Matching hashes establish identity, not absence of malicious behavior or vulnerabilities.

## 3. Application contract

- Request schema and maximum input:
- Response schema and successful caller action:
- Authentication, credential source and rotation owner:
- Timeout and caller behavior:
- Invalid input, rejected caller, unavailable service, and overload behavior:
- Synchronous only, or separately contracted durable workflow:
- Any agreed retry policy and safety / idempotency limits:
- Logging and retention, including prohibited payload fields:
- Source of representative synthetic or explicitly permitted test inputs:

Do not infer durable queues, cancellation, persisted results, or automatic whole-application migration.

## 4. Tests to agree before implementation

Each row must have a named procedure, threshold, and evidence path before execution.

| Check | Procedure and pass/fail threshold | Evidence location | Actual result | Reviewer |
| --- | --- | --- | --- | --- |
| Clean install from approved files | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Model / runtime / configuration identity | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Approved and unauthorized callers | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Invalid / oversized inputs | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| End-to-end application success | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Timeout and service failure at caller | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Representative workload / concurrency | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Agreed ingress / egress / logging | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Restart and restoration | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Failed update and rollback | UNFILLED | UNFILLED | NOT RUN | UNFILLED |
| Operator repeats the handover | UNFILLED | UNFILLED | NOT RUN | UNFILLED |

For each measurement retain model and source versions, hardware, workload, sample size, timing boundaries, resource observations, raw results, failures, and limitations. A completed checklist without inspectable evidence is not proof.

## 5. Release and recovery

- Baseline release and candidate release:
- Changed model / runtime / driver / configuration / caller components:
- Tests rerun and comparison with the same agreed workload:
- Failed or regressed checks:
- Required state backup, migration, or restoration (if any):
- Promotion decision and approver:
- Rollback trigger, procedure, and observed recovery:
- Remaining risks and approved exceptions:

An update is not accepted merely because the model loaded. Do not treat an empty result, missing evidence, or “not applicable” as a passed test.

## 6. Handover and acceptance decision

- Files delivered and rights / licenses:
- Runbook location:
- Operator walkthrough and reproduced checks:
- Monitoring, patching, backups, incident and support ownership:
- Allowed support hours / response expectations, if separately contracted:
- Access revocation and working-data removal:
- Open items:
- Acceptance: NOT REVIEWED
- Named reviewer and date:
- Scope changes / corrections required:

No automatic certification, scientific-quality result, 24/7 service, or permission to publish is implied. Publication of any customer details, test data, or results requires separate explicit authorization.