Supported checks clear
Approved
Required supported checks completed without a stop or review finding for this exact version under the current policy.
Available for Approved retrieval only while this is the current eligible version.Your document workflow
Check. Decide. Retrieve the Approved copy.
Scan an incoming document, follow its handling decision and download the current Approved copy for your AI workflow. Projects and Collections organise sources; the Pro API brings scoped submission, status and eligible retrieval into your systems.
A simple example
See the workflow from intake to reuse.
This illustrative example shows a source being checked, a decision to act on and an Approved copy ready for the workflow that needs it.
Illustrative workflow · Synthetic example
- 01
Check the incoming version
Choose a Collection for the client or project.Upload the source for scanning, then choose a Collection to keep related records together. An exact version means the file actually checked.
- 02
Follow the decision
Approved, Needs review or Quarantine.Use an Approved version, investigate a review finding or keep a blocked version out of your workflow.
- 03
Retrieve the Approved copy
Find it in your private Library.Download the current Approved file for your AI workflow, or use the Pro API for scoped document submission and eligible exact-version retrieval.
Three destinations
A decision, a reason, a next action.
Each completed supported scan routes the exact version. The evidence explains the decision; technical failure is shown separately.
A next decision is needed
Needs review
A finding needs attention, or required coverage is missing. Read the reason and next step before using this version.
Keep it organised while you review the concern, replace the file or retry as appropriate.In Quarantine
Quarantine
A registered hard-stop or blocking finding keeps this exact version out of normal retrieval and reuse.
Keep the record organised while you handle the finding, and keep this version out of your AI workflow.Technical failure: The scan could not complete, so no security decision was made. Retry is available and no new scan credit is consumed.
Every result is limited to the reported checks and coverage; it is not a universal safety guarantee.
Collections and Library
Organise sources. Supply the checked version.
Collections keep project records together, including files needing attention. The Library shows current Approved copies for retrieval into your agents and workflows.
- Keep Approved, Needs review and Quarantine records together in the right Collection.
- Use the Library to return to current Approved copies.
- Check a revised file again before using the new version.
Your Library
Reference guide.md
Approved · Supported checks clear
- Collection
- Knowledge-base sources
- Checked copy
- Current exact version
- Next step
- Retrieve for your workflow
Resolve uncertainty
Keep the next step useful.
See the concern or missing coverage, then follow the next step. Review the evidence, replace the document or retry where appropriate.
Deep Scan · Planned
Deep Scan is intended to add bounded contextual analysis to eligible findings that need closer review. It will not override a registered hard stop.
Before documents become AI context
Create a clear route for outside documents.
Check incoming versions, handle findings and retrieve Approved copies as your sources change. Start with five Standard Scans, once per account.