Completion review · Read-only · Browser local
Find the work that still needs attention.
Review a supported operations export. See which cases are marked complete without recorded acceptance, where records disagree, and what to check next.
- 01Choose permitted records
- 02Review the findings
- 03Take the next evidence check
Start with one supported export.
CSV or JSON · 1 MiB maximum · 5,000 records maximum. This review uses the six fields below; it does not infer an entire company from an arbitrary file.
Use the synthetic example or add a permitted export.
Supported fields and interpretation
case_id: stable case identifier. execution_status: completed, in_progress or failed. outcome_status: accepted, pending, rejected or unknown. age_minutes: nonnegative age as reported by the export. owner and source: text, or an empty string if unknown.
JSON accepts an array of records, or {"schema":"FinalityCompletionRecords/1","records":[...]}. Every record must contain all six fields. Invalid files are rejected as a whole; records do not silently disappear.
The rule assumes completion should be supported by recorded acceptance. Confirm that this describes your process. Source names and owner names in a file do not establish actual authority.
Then bring one useful finding into evaluation.
Confirm the governing source, responsible owner and actual intended outcome. In an authorized workspace, use the existing signed evidence and approval tools to test the conclusion.
This browser review is a conventional diagnostic, not first-party frontier intelligence, a signed Finality certificate, independent assurance or a measured business improvement. APEX, FSI, FII, FSIx, FIF, Reality Memory, Core and Control retain their separate roles and qualification requirements.