arrow_backRetour aux issues
finos/ai-governance-framework
#168
Débutant
Ouvrirarrow_forward
Débutant
Ouvrirarrow_forward
Débutant
Ouvrirarrow_forward
[Review] Ambiguity in System Acceptance Testing Mitigation
ecoDébutant
help wanted
good-first-issue
descriptionDescription
Point number 2 in this mitigation is quite ambiguous, especially as it calls out non-AI system being 100% pass rate whereas LLM systems being a lower threshold. This ambiguity is not especially palatable to FinServ orgs; so it would be more meaningful to call out testing against an "established fact store" and score the LLM system against it, for example.
Issues similaires
calkit/calkit
star53
Poids du dépôt moyen
VS Code extension should be robust to YAML parser errors
Seeing this error: ``` Failed to read calkit.yaml: YAMLParseError: A block sequence may not be used as an implicit map…
Python
bug
good first issue
fu351/Doberman-Core
star211
Poids du dépôt léger
dash: a manual Refresh control
The dashboard polls: `refreshStats()` (`src/doberman/dash/app.py:408`) every 5 s and `refreshPending()` (`:546`) every …
Python
enhancement
good first issue
fu351/Doberman-Core
star211
Poids du dépôt léger
dash: "Copy details" button on each pending-approval card
Each pending-approval card in the dashboard (`renderPending`, `src/doberman/dash/app.py:448-544`) shows the risk badge,…
Python
enhancement
good first issue