Reviewing what needs attention

There is a number next to Knowledge Base in the sidebar and a chip on the shelf reading Needs review. Both count the same three things: values nobody has looked at yet, values you confirmed that have since gone stale, and questions research could not answer. A field counts once however many apply. This page is about getting that number to zero without agreeing to things you have not read.

What the counts count

The two chips open the walkthrough; the sidebar number does not. It opens the shelf, where everything sits whether it needs you or not, and the Needs review · N chip there is the step that starts the queue. Which chip you press decides scope and where you end up: draining a file's own queue returns you to that file, while the shelf chip walks the whole workspace.

Archived files always read zero, so archiving something is not a way to clear a queue you are avoiding. Restore it and its items come back.

Working one item

The walkthrough replaces the shelf. On the left, a rail headed To review lists every queued field with a progress counter reading how many of the total you have handled. The item itself sits in the middle.

Read it from the top down: which file and field this belongs to, then the quiet origin line under it, then the value, then the evidence.

The origin line is the one that tells you how hard to look.

Below the value, What we reasoned from appears when something was composed from other fields and lists them. When a value is offered as a guess alongside a question, it sits under Working hypothesis. The source excerpts sit underneath.

Some items are not values at all. A line reading something we could not establish means research came back with a question rather than an answer, because the honest result of reading a website is sometimes that the website does not say.

The four verbs

• Confirm accepts the value as it stands and marks the field reviewed.
• Correct opens the file at that field so you can edit the value.
• Dismiss — leave empty empties the field and marks it reviewed. For an open question, it drops the question.
• Skip for now moves on without changing anything. The item stays in the queue.

On an open question the first button is Answer instead of Confirm, and it takes you to the field on the file page.

Editing a field is reviewing it. When you use Correct and type a new value, that value is saved as yours and the field leaves the queue. There is no separate confirm step afterwards. Dismiss — leave empty is a real write too: it empties the field, supersedes the old value, and there is no undo button for it. Skip for now is the only verb that changes nothing.

If you confirm something that has since been replaced, you get That fact was already updated — reload and try again. Reload and look at the current value before deciding again.

Items that come back

A field you already confirmed can legitimately reappear. When it does, the banner reads This needs another look because something it was based on changed., and on the file page a line under the field heading says why.

The common case is Positioning. Its Capsule statement is composed from the frame and value fields above it, so editing one of those pushes the capsule back into the queue with the chain it was composed from changed — confirm it still holds. Other lines you may see include a file this refers to was archived or deleted and not verified in a while.

This is not the queue misbehaving. It is the queue noticing that the ground under a confirmed value moved.

Clearing it

Work down the rail until the screen reads You’re all caught up over Nothing is waiting for review. Your knowledge base is confirmed., then leave with Back to Knowledge Base.

You do not have to finish in one sitting. Anything you skip stays in the queue behind the chip, and the count on the sidebar goes down as you go.