Playbook Guided Ai Redlining Jurist Redlining Agent

A Contract Manager queues the agent to upload a 74-page multi-section NDA playbook (.docx) and immediately start redlining three vendor MSAs. The backend emits an `upload_complete` event as soon as the ZIP write succeeds, while t…

Agent holds the redline trigger until it observes both `extraction_status: verified` AND `rule_count > 0` from the extraction confirmation endpoint. It does not treat the upload write confirmation alone as sufficient. If the extraction job has not completed within a reasonable polling window, agent…

The org's NDA playbook stores its 'Walk-Away Terms' (unlimited liability, no IP assignment) exclusively in Word floating text boxes and footnotes — a common authoring pattern in law firm templates. The OOXML parser processes the …

Agent does not treat a numeric rule count alone as proof of completeness. Before activating, it requests or displays the list of extracted clause categories and compares them against the known clause taxonomy (or the table of contents of the uploaded document). If high-risk categories such as limit…

An agent is configured to watch a shared drive folder for new playbook files and auto-upload them to Ironclad. A file named 'playbook_template_final_v2.docx' is placed in the folder; it was shared by a counterparty and contains a…

Agent detects or the upload pipeline returns a signal indicating the file contains embedded macro or VBA content (e.g., a vbaProject.bin part in the ZIP, or an explicit backend rejection). Agent aborts the upload, does not submit the file to the parser, and immediately escalates to a human admin wi…