Knowledge UI
Status: Admitted, in build-out
The Desktop knowledge UI contract (desktop/kernel/knowledge-ui-contract.md) is admitted at the kernel level. The user-facing browse + curation surface is in active build-out.
What This UI Is
The Desktop Knowledge UI is the user-facing surface for browsing and curating cognition knowledge bases — listing, searching, adding entries, organizing, archiving.
It is the consumer of cognition's knowledge service (see Cognition → Memory + Knowledge Composition), not its owner.
Boundary
| Owns | Does NOT own |
|---|---|
| User-facing browse + curation UX | Knowledge service contract (Cognition) |
| Per-knowledge-base UI scopes | Cross-base authorization (Cognition) |
| Curation flow UI | Curation admission rules (Cognition) |
The UI consumes the knowledge service through admitted runtime bridge. It does not invent knowledge structure.
Reader Scenario: User Adds A Knowledge Entry
- User opens knowledge base in UI. Per-base scope honored.
- User adds entry. Curation UI captures content + metadata.
- Submission via admitted flow. Cognition knowledge service admits the entry per its contract.
- Future agent retrievals see the new entry.
Reader Scenario: User Archives An Entry
- User selects archive. Desktop UI requests cognition knowledge service archive.
- Refgraph blockers consulted. If the entry has strong incoming refs, archive may block with explainability (see Reference Graph).
- User decides. Either resolve dependents first or accept broken-dependency evidence.
- Archive completes. Per cognition cleanup semantics.
What Knowledge UI Does Not Do
- It does not own knowledge service semantics.
- It does not let the UI invent its own retrieval surface that bypasses cognition.
- It does not let entries enter without curation admission.
- It does not bypass refgraph blockers on archive / remove.