ADR-242: A provider or a task tightens the privacy level
- Status
-
Accepted
- Date
-
2026-11-02
- Amends
-
ADR-064 (the level was global)
- Authors
-
Netresearch DTT GmbH
Context
ADR-064 has one level for the installation. An installation with a provider it trusts and one it does not has to choose the lower level for both, or store more of the second than it wants.
Decision
A provider and a task can name a level, and it can only tighten. Both
records get a privacy_ field, empty by default. The level a content is
stored at is the strictest of the global level, the level of the provider and,
for a queued run of a task, the level of the task, through
Privacy. A value looser than the global level does
nothing, so editing a record cannot open what an administrator closed. The field
offers no full for that reason.
Where it applies. Three stores keep content, and Run
answers for each:
- the events of a run, through
Run;Step Privacy Filter - the answer a queued run keeps, in
Queued;Run Coordinator - evaluation details, where the result names its generator's provider.
The audit rows of Skill keep the global level: they belong to
a skill, and no provider is involved. A segment resolves the level of its run once.
The provider of a run is the one its configuration's model names. A level that
cannot be read is none, because the question is what may be stored.
Consequences
- ●● An installation can keep run content for a local model and none for an external one.
- ◑ A configuration in criteria mode names no model, so only the global level and the task apply to it. Every preset of a Use Case Pack is one.
- ◑ A fallback that serves a call on another provider does not change the level of the run.
- ◑ A task at
noneormetadatakeeps no answer, so a queued result cannot be read. The globalmetadatakeeps it (ADR-234), and a level tightened tometadatadoes not, because the field says no content. - ◑ A copy made by an editor without access to the field follows the global level.
- ◑ Evaluation details of a run that does not name its generator stay at the global level.
- ◑ Governance shows the global level.
Net Score: +2
Alternatives considered
A level that can also loosen. Rejected: it would make an edit of a provider record a privacy decision the global setting no longer bounds.