Less file movement. A clearer review record.
Collection supports the agreed evidence scope. Your team controls the folder, the source credential and the runner. AGICOMPLY preserves the evidence record and keeps the remaining human decisions visible.
Choose one approved folder.
Define the AI system and review scope, then select the records your team has approved for this engagement. An authorized workspace user creates the source credential with multi-factor verification.
Run once, then send changes.
An inspectable runner operates in your environment. Its first command is a dry run. When you enable delivery, it checks the source credential, compares file hashes and sends new or changed PDFs. Watch mode can repeat that check while the process is running.
See what arrived and what needs review.
The workspace shows the recorded delivery and source receipt. The evidence inventory and content identities are recorded automatically. Human reviewers assess evidence relationships, gaps and the final package.
A repeatable handoff, with a receipt.
Identify the exact file
The runner hashes the file, and AGICOMPLY independently computes its SHA-256 identity. Unchanged local files are skipped; an exact delivery retry returns its existing receipt.
Preserve the revisions
A changed artifact is a new source observation. Recorded evidence currency changes can require re-review. Issued packages retain their original manifests and review dates.
Confirm delivery
Creating a credential means setup has started. A recorded evidence delivery confirms receipt. Failed or rejected transfers remain failures, with the next action visible.
A specific source your team controls.
The runner reads the selected folder on your computer or job host. If your existing document service already makes approved exports available there, that folder can be the delivery source.
- Source
- Regular PDF files directly inside one approved folder. Nested folders and symbolic links are excluded.
- File limit
- 4 MiB per PDF. Validation and relevance checks still apply.
- Setup
- Node.js 22 or later, a source configuration and a credential in your environment or secret store. Your team starts and operates the runner.
- Workspace
- An invited, active Baseline client in the U.S. data plane. Source feeds are unavailable in the EEA workspace.
- Control
- Stop the runner or revoke the source credential. Existing evidence and provenance remain preserved for review.
- Review
- Human acceptance, remediation and package issuance remain controlled steps. Later changes can need a newly agreed review.
See the source setup before you scope the work.
The runner source and setup instructions are public. Configure a real source only after written scope and approved intake instructions. The $750 Reviewer Evidence Check remains available when a focused first look is more appropriate.