Proposed and confirmed findings

The review queue is the heart of LexSalim's human-review model. Nothing the AI produces becomes part of the case record until a person says so.

The three states

State	Colour on screen	Meaning
Proposed	amber	Produced by the Case Agent, not yet reviewed.
Confirmed	teal	A member of the case has checked it against the source and accepted it.
Needs source check	sky	The agent could not fully support the item from the documents, or the source is a poor scan. Review with extra care.

The state is always shown as text as well as colour.

Reviewing a finding

1. Open the Review queue in the case, or the finding from the timeline.
2. Read the finding beside its source reference. The original page or clause opens next to it.
3. Choose Confirm, Edit and confirm or Reject. Rejected items are kept in the audit trail but hidden from the case record.
4. Optionally add a note explaining your decision; it is visible to other members.

Confirmed deadlines produce reminders. Confirmed events appear on the timeline. Confirmed drafts can be exported.

Why findings are not confirmed automatically

AI models can misread documents, miss context or state things the sources do not support. Keeping every output as a proposal until a person reviews it is what makes the case record trustworthy, and it is what a professional reviewer or a court would expect to see: who checked what, and when.

Who can confirm

Any member of the case. Practices often arrange that the person who requested the analysis is not the one who confirms it, which the audit trail makes easy to verify.

Audit trail

Each state change records the user, the time and the previous state. The trail cannot be edited.