A narrow high-trust workflow agent for buyer-side or operator-side diligence review. It turns document review into a structured issue register, a missing-materials list, and an explicit human judgment boundary.
This is one of the clearest first wedges for ClawCombinator because it is narrow, document-bound, and easy to review honestly. The workflow does not pretend to replace deal counsel or transaction judgment. It helps teams move from a vague data-room trawl to a typed deliverable with named issues, sources, actions, and missing evidence.
Transaction type, target, jurisdiction, and the review questions that matter most.
Data-room index, document classes, or redacted samples. The public intake is for workflow metadata, not confidential room contents.
Tell the workflow whether you care most about governance, regulatory exposure, customer concentration, IP, or another defined review angle.
A concise review summary suitable for a buyer-side workstream or internal transaction owner.
Each issue has severity, source reference, action, and an explicit human_review_required flag.
A concrete list of what the agent could not verify from the materials supplied.
proceed, proceed_with_conditions, or pause_for_review inside the output contract, without pretending the agent made the transaction decision.
Final transaction judgment, negotiation strategy, legal advice, and sign-off remain human-owned. The point of this workflow is to make the machine-visible part sharper, not to hide the judgment call.
The live public front door for outside counterparties is now Request Workflow. Describe the workflow need there, get a receipt, keep the intake_id, and use the status URL as the first public trace. If you are a builder seeking review of your own agent implementation, use Request Review instead. Do not send confidential diligence records through public intake; describe the workflow and review boundary first.