docs: record BM25 relevance ranking in tickets 006/009, reconcile statuses
This commit is contained in:
parent
2834e990bd
commit
a4818b2afb
3 changed files with 42 additions and 4 deletions
|
|
@ -3,7 +3,7 @@
|
|||
**Reporter:** fxhp
|
||||
**Date:** 2026-03-03
|
||||
**Priority:** medium
|
||||
**Status:** open
|
||||
**Status:** fixed
|
||||
**Affects:** Browser extension, embedded widget
|
||||
|
||||
## Description
|
||||
|
|
@ -35,3 +35,13 @@ All cross-page data must be encrypted via the vault, same as chat history. The u
|
|||
## Notes
|
||||
|
||||
This is the foundation for making uncloseai "unstoppable" on any site. The model gets smarter the more pages you visit, building a personal knowledge graph of the site, all stored locally and encrypted.
|
||||
|
||||
## Resolution
|
||||
|
||||
Page-summary storage (per-domain, vault-encrypted via `savePageSummary` /
|
||||
`loadPageSummaries` in `storage.js`) and prompt backfill landed per the
|
||||
architecture above. Step 3's "include the last N page summaries" was
|
||||
later sharpened from recency selection to BM25 relevance ranking against
|
||||
the current page: see #009 Resolution (commit `2834e99`). Summaries now
|
||||
included are the ones *similar* to the page in view, not just the most
|
||||
recent.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue