qdrant-lens
Dashboard UI — what you see
Three panels: knowledge tree (left) · history feed (centre) · chunk inspector (right). OKF files are labelled throughout.
|
When |
Action |
Actor |
Document |
Chunks |
|
2m ago |
upsert |
hamzah |
refund-policy.mdpolicies/okf/refund-policy.md |
+4 |
|
2m ago |
upsert |
hamzah |
kyc-threshold.mdpolicies/okf/kyc-threshold.md |
+2 |
|
2m ago |
upsert |
hamzah |
onboarding-sla.mdpolicies/okf/onboarding-sla.md |
+3 |
|
1h ago |
delete |
pipeline-ci |
old-refund-policy.mdpolicies/okf/old-refund-policy.md |
−4 |
|
3h ago |
set_payload |
hamzah |
compliance-rulebook.pdfpolicies/compliance-rulebook.pdf |
12 |
|
1d ago |
upsert |
pipeline-ci |
compliance-rulebook.pdfpolicies/compliance-rulebook.pdf |
+12 |
|
2d ago |
upload_points |
pipeline-ci |
src/ (128 files)github/src/… |
+128 |
What the UI shows you
OKF badge in tree
Any doc_type=okf group shows a teal OKF badge next to its count. You can tell at a glance which sources contain curated knowledge vs raw docs.
Added (upsert)
Green dot + green upsert pill. Chunk delta shown as +N in the chunks column.
Deleted
Red dot + red delete pill. Chunk count shown in red as −N. Doc path still visible for traceability.
Updated (set_payload)
Blue dot + blue set_payload pill. Metadata-only changes (tags, author fix) appear here without re-embedding.
OKF card in inspector
When _lens.is_okf=true, the inspector shows a card with title, description, OKF type, and a clickable resource link — before the raw chunk text.
What's not yet there
The live UI doesn't show the OKF badge or card yet — those are the frontend changes needed to surface the OKF work we built in the backend.