Contracts

Contracts is a preview workspace for AI-assisted review of routine commercial agreements. Built-in playbooks cover mutual NDAs and seller-side customer order forms. Named custom playbooks support other agreement families by specifying your role, review instructions and required clause headings. A custom playbook does not certify that every document type or legal issue is supported.

Use synthetic documents for the application demonstration. This guide describes implemented behavior, not confidential-customer security clearance or a guarantee of legal completeness.

Choose the workspace and playbook

Sign in with your Topolo account and select the organization and Contracts workspace. A workspace administrator must approve a playbook before you use it. NDA settings include confidentiality duration and governing law. Order-form settings include payment days, liability-cap multiple and governing law. For another agreement family, create a named custom playbook with clear review instructions and required clauses.

Reviews retain the exact approved policy version, approver and approval time. Later policy changes do not silently change existing reviews. Playbook approval requires appropriate legal judgment.

Save a contract before starting AI

Add the agreement title, counterparty, selected playbook and a DOCX file up to 1.5 MB. Contracts retains the original privately with its hash before analysis. It reads main-body paragraphs, original and proposed wording, and tracked insertions, deletions and moves. Main-body table cells are included as paragraphs.

PDFs, scans and arbitrary Word structures are not supported. Documents with headers, footers, comments, footnotes, endnotes, drawings, embedded objects, fields or external relationships are refused instead of silently omitting potentially material content. Extracted text must be between 100 and 60,000 characters. Do not remove material terms merely to pass ingestion.

Start analysis from the saved intake. Uploaded, analysing, failed and completed states are retained. A failed attempt keeps its intake and original document. Read the failure and current state before retrying; an active analysis lease prevents overlapping attempts. Analysis executes within a bounded request, not a proven unattended job queue: leaving the browser is not evidence that it completed. Refresh the intake to confirm its state.

What the intelligence does

TopoloNexus runs structured clause extraction and drafts replacements using the approved playbook, current paragraph text, original wording and tracked changes. The request uses an explicitly selected model, output limits and a caller spending budget. The app does not silently switch models after a refusal. Successful reviews record the model, provider, Nexus request ID and prompt version. Access, billing, transport or malformed-output failures do not become successful findings.

Model findings explain the effect of proposed changes and quote the source. Suggested replacements must have one exact source location. Deterministic checks separately flag prohibited data-use and residual-knowledge language, and uncapped liability where applicable. Built-in policy rules provide routing; custom playbooks require human judgment.

Missing required clauses, unverified quotations, and wording or tracked changes not accounted for by uniquely anchored model evidence remain explicit review obligations. Source accounting detects gaps in extraction; it cannot guarantee semantic or legal completeness. Incorporated agreements and missing schedules must be checked by a person.

Review, decide and download

Open a finding in the shell's overlay evidence panel. Compare the complete original and proposed paragraph, the approved policy position and any replacement draft. Accept a valid anchored replacement or reject the suggestion to retain the counterparty's proposed wording. Rejecting a suggestion does not restore earlier deleted wording.

Read the full paragraph before acknowledging an unreviewed-source finding. Resolve actionable findings and missing coverage before approval or reviewed export. Built-in prohibited provisions require an acceptable replacement or legal escalation; keeping prohibited wording does not make it approvable. Updates use the review version so stale decisions are refused.

A person approves the review; AI never approves or signs an agreement. Approval locks further decisions. Download the reviewed DOCX to obtain accepted replacements as tracked insertions and deletions, with counterparty revision authors and untouched wording preserved. Missing, repeated, changed, overlapping or unsupported source anchors cause export refusal, not a guessed replacement.

The audit trail records intake events, finding decisions, source acknowledgements and approval with the acting identity. Original-document download is distinct from reviewed-redline export.

Privacy and access

Verified identity supplies the organization; product records, source documents, decisions and audit reads are scoped to both organization and workspace. Intake input cannot choose a different tenant. Originals use private object storage and product records use the canonical data package with Contracts-owned tables.

Development deliberately does not use application-layer encryption. Staging is the first encrypted environment; production also requires the configured envelope-protection boundary. An engineering implementation or local encryption test is not independent privacy assurance.

Workspace administrators can configure retention. An erasure preview identifies the exact records before permanent deletion, which requires explicit confirmation and the current snapshot. Erasure removes the associated product records and original object; a pending storage cleanup remains visible for retry. Do not erase a document you need to retain as evidence.

Automation and limitations

The published Contracts catalog exposes policy, intake, review, finding decision, audit, original-download, reviewed-export, retention and erasure operations. Discover actions, their schemas and the credential's workspace resources through Topolo CLI or MCP. Validate and plan the exact operation before execution; do not substitute an admin account for reviewer proof.

Contracts is not a replacement for legal advice, a signature service, or a guarantee that AI will find every issue. Broader Word compatibility, independent assurance, real-provider staging proof and an ordinary-reviewer end-to-end walkthrough remain release-readiness requirements. Catalog or health reads do not prove a completed AI review. Topolo Sign integration is outside this demonstration.