Open points

In short

• This page tracks the decisions taken on the needs and what remains to do to meet them.
• Each point cites the need concerned, such as DPO-10 or OPS-6.
• What is done is not listed here. The need and its acceptance tests show it, and the git history keeps the detail.

Decided, to do

Decided on October 2, 2026.

• DPO-10 DPO-10 Needs by profile As a DPO, I want to choose in which form human corrections are kept, so that their storage does not become a copy of the data.: design the export of human validations, to Langfuse for example. Three forms will be available, placeholders instead of the values, values in clear, or input and output fully masked. The default form is placeholders.
• OPS-6 OPS-6 Needs by profile As an operator, I want to load a reviewed configuration from the catalog by its reference, so that I do not maintain a local copy.: accept model configurations on the catalog. Their current rejection is temporary. It needs a format that splits the labels between patterns and model, because each NER model is stronger on some labels.

Proposed, not yet decided

These proposals add criteria to existing needs. Each criterion describes a behavior that tests already check. What remains to decide is whether it goes into the text of the need.

• DPO-1 DPO-1 Needs by profile As a DPO, I want no personal data and no secret to leave in clear text toward the LLM, so that I stay compliant with the GDPR and do not expose access credentials.: add two criteria.
  • No value goes back to the model in clear, neither in later turns of the conversation, nor in a message split into several blocks, nor in the argument of a tool call.
  • A placeholder the user types themselves, such as <<PERSON:2>>, does not reveal the value of another person.
• OPS-4 OPS-4 Needs by profile As an operator, I want to protect the API with keys, a maximum request size and a rate limit, so that it is neither open nor abused.: add two criteria.
  • The piighost-api server refuses to start if an API key is malformed, unless PIIGHOST_ALLOW_ANONYMOUS is set.
  • A protected route called without a key answers 401.