# Capordia — GPU Acceptance Dossier, Version 1

Version: 1.0.0. Resources prepared on September 24, 2026.

These documents are used to reconcile the agreed requirement, the allocated environment, and the results of your task. They do not contain any GPU measurements. The "Blueprint Workshop" example is entirely fictional.

## Prerequisites

- A text editor for Markdown files.
- A spreadsheet or CSV reader: UTF-8, comma as separator, first row as headers.
- For inventory commands only: authorized access to your target, the NVIDIA SMI or AMD SMI tool, and the appropriate drivers already installed. No installation is required to read or fill in the templates.
- A test dataset that your team has the rights to use, an application procedure, and the criteria decided before the test.

## Files

| File | Purpose |
|---|---|
| modele-reception.md | Cover page, scope, responsibilities, and decision |
| grille-reception-vierge.csv | Ten checks to adapt, with no invented observations |
| exemple-fictif.md | Review of a dossier whose commissioning remains blocked |
| exemple-fictif.csv | Ten rows from the same scenario, no hardware compliance asserted |
| grille-refus.csv | Six deviation cases, expected follow-up, and responsible role |
| commandes-lecture-seule.md | NVIDIA/AMD inventory to run on your target |
| LICENSE.txt | Permission to use and adapt these original resources |

## Using the template

1. Copy the template and the grid into your project folder. Keep a blank version.
2. Name the role holders. Define model, number of cards, application, inputs, outputs, and criteria.
3. For each check, distinguish `fabricant`, `allocation`, and `tache`. A manufacturer reference does not validate the allocation or the result.
4. Replace the generic criteria with those of your project before running the tests.
5. After each test, keep the raw observation with its unit, the date, and a document reference. Do not record any secret, key, or cookie in the shared dossier.
6. Decide the status. An empty box is not a success. Document any checks that are out of scope.
7. Have the decision signed by the authorized role, then hand the dossier over to operations.

Recommended statuses: `non execute`, `conforme`, `bloque`, `refus`, `reserve`, `hors perimetre`.
The `conforme` status assumes the expected evidence and the criterion has been met. A reservation specifies the limited use, its owner, and the re-check. A mandatory check not performed blocks acceptance of the entire chain.

The CSV contains no formula, no automatic status, and no formatting. Actual numeric fields must retain their units in the dedicated column. Dates must be entered explicitly, for example ISO 8601 with time zone.

## Limitations

The hardware commands are documented and not executed on a GPU target for this publication. No time, throughput, memory consumption, topology, or CUDA/ROCm result is certified by these files. They establish neither payment, nor service guarantee, nor absence of interruption.

Related guide: /guides/cahier-des-charges-gpu
Next: /guides/preparer-migration-calcul-continu