# Logistics and supply chain 1.0.0 policy templates

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

| Template | Kind | Name | Needs your key reference |
| --- | --- | --- | --- |
| `LOG_LINKED_TEST_DATA` | MASKING | Linked logistics test data | yes |
| `LOG_ANALYTICS_UNLINKED` | MASKING | Unlinked logistics analytics extract | no |
| `LOG_LOCATION_MINIMISED` | MASKING | Linked test data without location-like delivery detail | yes |
| `LOG_CLASSIFICATION` | CLASSIFICATION | Logistics and supply chain classification | no |
| `LOG_STRICT` | CERTIFICATION | Logistics and supply chain certification: strict | no |
| `LOG_SCENARIO_TESTING` | CERTIFICATION | Logistics and supply chain certification: scenario testing | no |
| `LOG_SUBSET_DEFAULT` | SUBSET | Logistics and supply chain subset (default bounds) | no |
| `LOG_REFRESH_WEEKLY` | REFRESH | Logistics and supply chain 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/logistics-supply-chain/policy-drafts` with `key_ref`
creates DRAFT policies from these templates; approve them through the normal policy workflow.