> Source: https://vitna.ai/docs/concepts/provider-term > Raw Markdown: https://vitna.ai/docs/concepts/provider-term.md > Corpus index: https://vitna.ai/llms.txt # Provider term What a provider published about **how** it handles the work, beside what it charges for it. Retention, training use, processing regions, whether a key you hold is accepted. A workload can require one, and a candidate whose provider does not meet it is excluded before anything is weighed. ## It is not a price A [price](price-period.md) is a figure with a unit. A term has neither: it is a yes, a no, or a list of regions. It passes the same admissibility rule the tape applies, because it is a statement on a document the provider publishes on its own domain that can be fetched, archived and dated. It fails the tape's shape, because there is nothing to divide. So it sits beside the tape and never on it: no board shows one, no spread compares one, no [reference rate](reference-rate.md) is computed from one. ## It is curated, not parsed A policy page is prose and the answer is a yes or a no. An adapter deciding what "we do not retain your data" means would be interpolating exactly where the honesty contract forbids it. So a term is entered by a person with `npm run term:add`, under the four refusals the [curated log](market-event.md) already applies: no source URL no row, http is not a source, a host that is not the provider's is not the provider, and a URL that does not answer 200 today is not verified today. ## The four kinds | Kind | Value | Answers | |---|---|---| | `zero_retention` | `yes` or `no` | Whether prompts or responses are kept after answering | | `no_training` | `yes` or `no` | Whether customer data is trained on | | `regions` | `us,eu` | Which regions the work is processed in | | `byok` | `yes` or `no` | Whether a key the customer holds is accepted | Each kind is named for what a `yes` means, so `zero_retention = yes` is a provider that retains nothing. `observed_on` is the date somebody read the page, which is the date the term is true as of. It is never a date the provider states: policy pages rarely carry one, and a date nobody published would be invented here. ## What a workload does with one ```bash npm run aperture:workload:edit -- acme/support --constraint requiresZeroRetention=true ``` | Constraint | Meaning | |---|---| | `requiresZeroRetention=true` | The provider must publish `zero_retention = yes` | | `requiresNoTraining=true` | The provider must publish `no_training = yes` | | `requiresRegions=us,eu` | Every region the provider processes in must be one of these | | `allowsProviders=anthropic,openai` | Who may see this work at all | `allowsProviders` is not a term, and that is deliberate: no provider publishes a document saying whether this customer approves of it. It is a fact about the organisation, so it lives on the workload alone. A list that does not name `openrouter` keeps the substrate out as well. Since vitna-runtime 0.3.0 the signed policy then carries no OpenRouter name for that workload's lanes, fallbacks or rules, so no runtime can route its work through OpenRouter whatever keys it holds. ## A requirement the record cannot check is not satisfied This is the whole of the design and the only part worth arguing about. A workload that requires zero retention, weighed against a provider whose retention the record has never read, could be answered three ways: pass it, fail it, or ignore the requirement. The first two both invent a fact. **The third is the one that looks harmless and is worst**, because the brief would then be silent about a constraint the customer wrote down. So the candidate is excluded, and the refusal names what is missing: > this workload requires that its provider retains no prompt or response data, > and the record holds no zero_retention term for fireworks. A requirement the > record cannot check is not satisfied, and assuming either answer would put a > fact in the record that nothing supports. That is the same rule `costPerUnit` already applies to a price the tape does not carry. ## What it closes Before this existed, exactly one of these was representable, and it was `VITNA_ALLOW_PROVIDERS`: an environment variable an operator typed on a box. The [runtime](../runtime/serving.md) honours it before every route including a fallback, which is the right enforcement, and nothing in the record knew it existed. An operator who wrote down a compliance boundary had said something no decision recorded and no brief could cite. Part of the decision was living outside the decision record. A decision made under a requirement now names the `witness.provider_term` rows that answered it, in `inputs.termIds`, and the brief prints them. "Why was this candidate allowed to serve" resolves to a document somebody read on a date, exactly as a figure resolves to a period.