A safety layer for document automation

Stop the wrong document before it reaches a signer.

SignLatch sits between an AI agent and Foxit eSign. A person verifies the PDF, recipient and signature fields—then releases only that exact version.

For legal operations, procurement and document teams

Try the safe approval simulationSee how it works
Release checkpoint

Needs your review

Locked
Supplier AgreementExample Components · prepared by agent
Signature fields
2 fields on page 1
Terms
Net 30 payment terms

The agent cannot send this.
A person must approve the exact document and recipient first.

Review before sending

If any bound material fact changes, SignLatch cancels the approval.

01Agent preparesDraft the PDF and place fields with Foxit MCP.
02Human verifiesCheck the exact file, recipient, terms and fields.
03Foxit sendsRelease only the version that was approved.

Foxit MCP authority boundary

Public fixture · live operation separately gated

The fixture behind the approval.

Sanitized real fixture

Prepare a supplier agreement for Example Components with Net 30 terms.

Artifact SHA-256
8f0b2b32d4a1f6c6b90a09caa36438f74d46bc62d5f726d42a2cc9bb3e7b1301
Provenance
upload_document → pdf_from_text → download_document
Authority
Human approval is required · Signing dispatch is latched
Continue to human approvalSign in for the private workspace

Public showcase is read-only

No control here can consume Foxit credits, access private artifacts or contact a recipient.

0 provider effects

Fixture-demonstrated · zero SignLatch/provider effects

Try the exact approval latch

Review the exact fixture, record a simulated approval, then challenge it with any material mutation. The provider boundary remains locked throughout.

Application stateReview requiredNo approval is recorded.
Provider stateLockedZero SignLatch/provider effects

Exact fixture is ready for human review.

Bound snapshotapproval-v2 / exact fixture

Review and approve the exact snapshot before introducing a mutation.

AWAITING APPROVALProvider: LOCKED
Challenge the approval with a real-world change

Start with the recipient change, or open any other material-change case. Every case must invalidate approval.

Fixture boundary: no SignLatch provider-effect request, signing action, or credit use can originate here. Hosting infrastructure may emit operational telemetry.

Authenticated Foxit eSign proof

Live demonstrated

One envelope. Human-signed. Verified from Foxit activity.

SignLatch retrieved the real envelope state from Foxit's authenticated activity API, imported eight lifecycle events, downloaded the executed PDF, validated its structure, and independently hashed the retrieved bytes before marking the workflow complete.

Provider lifecycle
Executed
Authenticated activity history
Timeline events
8
Sanitized and digest-bound
Executed PDF
60,071 bytes
Validated before completion
SHA-256
058c3e619e459d01…6175e79
Content-addressed evidence

Privacy boundary: the public proof exposes the executed-file hash and aggregate lifecycle facts—not recipient data, provider or event identifiers, signatures, or document contents.

View sanitized evidenceInspect completion source

Technical event log

Every transition leaves a reason.

  1. Foxit PDF preparedReversible
  2. Review digest createdBound
  3. Human approval recordedLocal fixture
  4. Recipient mutatedInvalidated
  5. Provider dispatchDenied

Enforcement boundary

Preparation and commitment never share authority.

Reversible sidePrompt → Foxit MCP → Policy checksMay prepare and inspect. Cannot authorize.
Human latchExact digest + recipient + intentAny material mutation invalidates approval.
Commitment sideFoxit eSign · verified liveA real envelope was sent, signed and executed under a one-envelope budget.