Knowledge-base edits
Two related capabilities, sequenced in two phases.
Phase 1: Notes → KB (the flagship)
The cross-product feature top-billed throughout these docs. Tap “Add to chatbot knowledge” on any note; it’s chunked, embedded, and indexed into the bot’s vector store. → Full plan
This is the capture path — taking content the operator captured anywhere and turning it into bot knowledge.
Phase 2: Direct KB edits on mobile
The curation path — managing the existing KB:
- Browse the KB — see every chunk indexed, with source (note, document, website, manual entry).
- Search the KB — find a chunk by content.
- Edit a chunk — fix a typo, clarify a fact, add a synonym.
- Approve / decline chunks pending review (if you’ve configured a review queue).
- Delete a chunk — pull stale content out of the bot’s brain.
How it’ll work (preview)
A new sub-section under Chatbot management → Knowledge base. Lists every chunk with status (Active, Pending, Archived), source, last edit, and quick actions.
Editing a chunk on mobile re-runs the embed pipeline; the change reflects in the bot’s responses within ~30 seconds.
What’s intentionally NOT in scope (for now)
- Adding a whole new website / Google Drive / Notion as a knowledge source. These OAuth-and-configure flows are deep web operations; mobile would just deep-link to the web for these.
- Bulk operations (delete 200 chunks). The web is for that.
The mobile KB editor is for the moment-to-moment curation: “this answer the bot’s giving is wrong; let me fix it from my phone.”
Status
- Phase 1 (Notes → KB): depends on the cross-product embedding pipeline (in development; first to ship).
- Phase 2 (direct KB edits): depends on Chatbot’s existing KB-management API + a mobile UI; ships after Phase 1.