DOCUMENT OPS
Daily re-hash audit of the contract archive for silent drift
Runs nightly across the archived contracts in S3, re-hashes every PDF against its registered baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires the audit
- ActionList all PDFs under S3 archive/ prefixAWS S3
- ActionRe-hash each file and compare to baselinePostgres
- LogicCollect mismatches into a drift set
- OutputWrite report to Notion and alert SlackNotion
What it does
Even verified contracts can be altered in storage by a bad sync, an errant edit, or a malicious change. This scheduled audit re-walks the entire archive on a cadence, recomputes each PDF's SHA-256, and compares it to the baseline recorded at verification. Any file that no longer matches is reported as drift, catching tampering that slips in after the initial intake check passed.
When to use it
Run this as a recurring safety net over your contract archive of record, especially for compliance regimes that require periodic proof that stored documents are unchanged. Complements the per-upload sentinel by catching at-rest modifications.
How it works
- 1A nightly schedule triggers the audit.
- 2The workflow lists every PDF under the S3 `archive/` prefix.
- 3For each file it recomputes the SHA-256 and compares against the registered baseline in Postgres.
- 4A logic step collects every mismatch into a drift set.
- 5If any drift is found, it writes a dated findings report to Notion and posts a summary with the affected contract IDs to the compliance Slack channel; a clean run posts a green all-clear.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect NotionPages, databases, comments.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.