07_Known_Issues - ravkorsurv/kor-ai-core GitHub Wiki
Known Issues โ Kor.ai
This page captures acknowledged limitations and current issues affecting the Kor.ai surveillance platform. Each issue is tagged by type, status, and ownership.
โ ๏ธ Bayesian Model โ Limitations
| Issue ID |
Description |
Status |
Owner |
| M001 |
Node inputs rely on clean mapping from upstream data |
Open |
Data Team |
| M002 |
CPTs are seeded manually and not auto-trained (yet) |
Known gap |
Risk SME |
| M003 |
Explaining-away effect not always intuitive to analysts |
In progress |
UX Lead |
๐ Agena API โ Integration Gaps
| Issue ID |
Description |
Status |
Owner |
| A001 |
API token expires every hour, needs caching |
Done |
Core Dev |
| A002 |
Cloud API rate limits not fully known |
Known gap |
Awaiting vendor |
| A003 |
No logging of raw API calls in prod |
Open |
Core Dev |
๐๏ธ UI โ Functional Bugs & UX Gaps
| Issue ID |
Description |
Status |
Owner |
| U001 |
Filter resets on table refresh |
Open |
Frontend |
| U002 |
Case notes not auto-saving |
Planned fix |
Frontend |
| U003 |
Score not color-tagged on detail page |
UI backlog |
Frontend |
๐งช Testing โ Known Gaps
| Issue ID |
Description |
Status |
Owner |
| T001 |
Spoofing model not yet tested on real data |
Planned |
Product/Risk |
| T002 |
Edge case: sparse data with high score |
Need validation |
Model Lead |
| T003 |
No end-to-end alert audit trail across all systems |
Known gap |
Infra Lead |
๐งญ Notes
- Issues are triaged weekly in sprint planning
- Critical issues are flagged in
Release Notes
- All modeling limitations are tracked under each model version (see Bayesian Model Design)