Source-bound value
The proposed value exactly matches field-eligible, cited authoritative evidence from the current source revision.
Reviewable document extraction
Select a folder, name up to eight fields, and process as many as fifty source files sequentially. FileNyani validates model proposals against cited evidence before assigning a trust state.
AI proposes. Evidence determines status. Human review stays separate from the original AI result.
| Source | Customer | Notice |
|---|---|---|
| agreement-a.pdf | Found Acme Corporation | Needs review 30 days |
| agreement-b.docx | Found Contoso Limited | Not extracted |
Trust states
Exact text must match cited authoritative content selected for that requested field. Otherwise the value remains a candidate for review or is reported as not extracted.
The proposed value exactly matches field-eligible, cited authoritative evidence from the current source revision.
A candidate exists, but evidence does not satisfy the Found boundary. OCR-only values always stay here.
The model supplied no usable value, or could not complete a valid structured response for that field.
The field may be missing from the bounded evidence, outside the supported source content, or unavailable because the local model did not complete that field.
Human review overlay
Confirm a source-bound value, accept an original candidate, enter a correction, mark no value, or clear the overlay. Reviews remain revision-bound and export separately from AI output.
Save labels such as “Contract basics” and reuse them in another folder. Reuse fills the composer but never starts work automatically.
Changed or missing sources disable stale review actions instead of silently binding old evidence to new content.
CSV and JSON preserve field order and keep AI status/value separate from human review status/value.
No hidden workflow schema or cloud extraction service. You choose the scope, fields, model, and final review decisions.