Reviewing suggested knowledge
Open Knowledge → Review Queue to check pending suggestions. Read each statement and its linked source before deciding whether it belongs in your knowledge base. Stored confidence is separate from search ranking; neither proves a statement is true.
Compare related information
Scan each item's type and text, then open Text & source for the full statement, source context, links and stored confidence. Select Compare, then expand an individual Compare item entry for its full text and source. Expanded text replaces its short preview rather than repeating it. Only one item's comparison is active at a time.
Open Compare relationships when you need the two items' outgoing and incoming relationships to approved items. These are loaded on demand, not while scanning the queue or reading candidate text. Full related text, direction, type, labels and source links are available; technical IDs are behind a separate disclosure. Identical stored edges appear once; self-links are labelled. Other pending/rejected items are excluded, and unavailable targets or load errors are stated explicitly: this is not proof that no relationship exists. Open item and relationships still opens the existing detail page, whose outgoing-neighbor view is not a complete inbound inventory. Missing source links are stated explicitly.
Identical wording does not establish identical context. Different wording may describe the same statement, related information, an addition or a contradiction. Check the full text and both sources; this comparison does not supply an AI agreement judgment.
How this was found explains relative search ordering, not duplicate certainty. Search combines meaning, shared-word overlap and related-item ranks. The API normalizes the top result to 0.95, including when it is contradictory; this is not raw reciprocal rank fusion, a match percentage, an agreement judgment or stored confidence. The API does not report which signals were available: meaning search can fail and leave word-overlap results. Individual scores are not displayed.
Merge is unavailable because it cannot yet safely preserve source links and relationships. Comparison does not change or remove either item. Keep separate for now closes the comparison only: it does not approve either item or save a permanent duplicate decision.
Comparison searches are available for pending and approved items. A rejected or deleted item cannot start a new comparison search; refresh the queue if an old item remains visible.
Comparison results use the existing session query cache. Recent results can be reused when switching items; known knowledge changes invalidate them. Stale results may refresh. Reopening a panel or seeing a loading indicator does not, by itself, mean the search ran again. Changes from another browser are not detected immediately.
Approve, edit or reject
- Approve makes the item available as approved knowledge.
- Edit, then Save & Approve, lets you correct the suggestion first.
- Reject opens a confirmation with the full item text. Rejection hides the item from review and knowledge results. Original sources and artifacts stay, and there is no undo here. Expand What happens to links and stored data? for details: records remain marked rejected, links are not transferred and other items linking to them are not rewritten. Search-index cleanup is attempted after saving the rejection; a cleanup failure does not undo the rejection or make the item eligible for retrieval.
- Cancel leaves the item unchanged. If rejection cannot be confirmed, the page keeps a warning and pauses knowledge review actions. Use Reload the queue to check the saved result; if reload fails, the warning stays. Choose only remaining items after a successful reload — do not assume an error means nothing changed.
Single and batch rejection use the same path. A request rejects at most 500 unique records in one conditional database batch; missing or already-deleted records are not rewritten. If a record changes during the request, the batch fails rather than saving only some items. A lost response can still leave the whole batch saved, which is why reloading is required. This guarantee covers rejection, not approval or wiki proposals.
Upload review also pauses if it cannot confirm every choice. Reload the items reads the saved items without repeating approval, rejection or ingestion. A failed reload keeps review paused. Approval and rejection are separate requests, so some choices may already have saved.
Approve All and Reject All apply to the loaded pending list of suggested knowledge, not a selected set of checkboxes, and never to wiki proposals. Reject All asks you to review the affected items before confirmation.
On narrow screens, labelled review controls wrap instead of requiring horizontal scrolling. Individual comparisons are keyboard-expandable.
Wiki proposals
When you ask chat to create a wiki page or to change one, it does not change the wiki itself. It proposes the change, and the proposal waits in the Wiki proposals section of this screen, marked Wiki Agent, until someone decides it. Any member of the workspace can approve or reject a proposal.
Open Changes (for an edit) or Preview of the new page to load what the proposal would write. Approve stays unavailable until you have opened it, because approving should mean you have seen the change.
- A page edit shows the changes line by line: added lines marked +, removed lines marked -, with a few unchanged lines around each change and longer unchanged stretches collapsed. A proposed edit replaces the whole page, so check that nothing you want to keep was removed. If it removes embedded references — an insight, an artifact or a document excerpt shown in the page — the card lists each one.
- A change too large to show whole says Too large to review here, and it cannot be approved on this screen. Reject it and ask the assistant in chat for a smaller edit.
- A new page shows a preview. Its [[links]] are checked when the page is created, so they are not checked here.
- Hidden characters are shown as markers such as ⟨U+202E⟩. Some characters are invisible, or change the direction text is displayed in, so text could read differently from how it is stored. When a proposal holds any, a warning on the card says how many; check each marker before approving, and reject the proposal if you did not expect them.
- Evidence lists what the proposal is based on — a passage from a wiki page, an insight, a source document or the request made in chat — and why it supports the change.
Approve edit writes the change to the page as a new version, recorded as an applied proposal under your name; the page's history keeps the version before it. Approve and create draft creates the page as a draft. Reject asks for a reason, records it and changes nothing.
A proposal is made against the version of the page the assistant read. If the page has changed since then — edited, renamed or deleted — the card says The page changed since this was proposed, and it can no longer be approved, so a newer edit is never overwritten. Reject it, or ask the assistant to read the page again and propose the change anew. If a page with a proposed page's title now exists, the card says so: ask for an edit to that page instead.
Automatic context and source availability
Summaries generated from imported sources use approved, non-deleted knowledge, not pending or rejected suggestions. Pending suggestions remain available in the Review Queue. Knowledge extracted from artifacts always needs explicit approval here, regardless of confidence or publication status; publishing an artifact does not approve its claims. Document ingestion keeps its separate review policy.
When the backend automatically retrieves context, it checks the current knowledge records and resolves source passages against their stored source and chunk records. Deleted, missing, unfinished, failed, review-isolated and Browser Clip sources are not eligible for that automatic source lookup; a leftover search-index result is not sufficient. Complete means processing finished, not that a person verified the source.
Knowledge approval and source availability are separate. Rejecting an extracted item does not withdraw its original source text, and approving one item does not release a review-isolated source. These checks apply to backend retrieval and imported-source summaries; they do not remove text already present in conversations or revalidate context already supplied by a client.
Older information
The stale section lists items not validated in 90 days. Read the content and source before using Re-validate; age alone does not establish that information is wrong.