# Automotive 1.1.0 policy templates

Contract policy bodies (selectors, strategies, thresholds). They contain no data and no keys.

| Template | Kind | Name | Needs your key reference |
| --- | --- | --- | --- |
| `AUTO_LINKED_TEST_DATA` | MASKING | Linked automotive test data | yes |
| `AUTO_QUALITY_ANALYTICS` | MASKING | Unlinked warranty and quality analytics extract | no |
| `AUTO_TELEMATICS_MINIMISED` | MASKING | Linked test data without connected-vehicle location and driving behaviour | yes |
| `AUTO_CLASSIFICATION` | CLASSIFICATION | Automotive classification | no |
| `AUTO_STRICT` | CERTIFICATION | Automotive certification: strict | no |
| `AUTO_SCENARIO_TESTING` | CERTIFICATION | Automotive certification: scenario testing | no |
| `AUTO_SUBSET_DEFAULT` | SUBSET | Automotive subset (default bounds) | no |
| `AUTO_REFRESH_WEEKLY` | REFRESH | Automotive weekly refresh | no |

Keyed templates reference the placeholder `vault://datanivra-pack-template/linkage-key`. Replace it with a
reference to a key in **your** secret store (for example `vault://…`, `azure-kv://…` or `env://…`).
The simplest way is server-side: `POST /v1/industry-packs/automotive/policy-drafts` with `key_ref`
creates DRAFT policies from these templates; approve them through the normal policy workflow.