# Model configuration

The YAML file next to the RKNN model is part of the deployment contract.

- `task` selects the task backend.
- `model` is relative to the YAML directory.
- `input` records width, height, layout, format and normalization.
- `postprocess` records adapter and thresholds. For Seg models,
  `class_agnostic_nms: true` suppresses highly overlapping lower-score boxes
  even when their predicted class IDs differ; `false` suppresses only within
  the same class.
- Imported source contracts may use `labels_file`. Studio resolves it during
  import and writes one canonical inline `labels` list into the delivery YAML.

Do not replace files inside an existing delivery manually. Import a new model
version into the same business project and regenerate both platform archives;
the fixed paths remain unchanged and `manifest.json` records the new hashes.