START WITH THE PRODUCT STEPS Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration. Q06 - Check e-signature completion evidence against the approved signer packet Status: Proposed / not tested WHAT THIS KIT CONTAINS Exact input scaffolds and synthetic examples for an offline pilot. Header, JSON-shape and fixture-consistency checks validate these files only; they do not test an assistant, product integration, legal decision, PDF inspection or live workflow. PREREQUISITES 1. Lawyer-approved required signers/roles and source document version; staff-verified envelopeā†’document mappings; exported envelope/recipient history; final signed artifact IDs and certificate IDs. DocuSign or equivalent with explicit mappings, spreadsheet join. A signed PDF's hash naturally changes from the unsigned source: compare approved source version via the mapping, never require source and signed hashes to be equal. SETUP 1. Use the separate synthetic example inputs first. Fill a copy of the blank template or input checklist for your own preparation; do not mix fixture information with real records. 2. For this synthetic fixture only, completed is the supplied recipient completion status. W1 is intentionally absent and there is intentionally no certificate row. Real platform vocabulary must be supplied and reviewed. 3. Preserve exact CSV headers. CSV templates contain only a header row. Import ID, hash, page-label and timestamp columns as text; inspect leading zeros and do not enable formulas from untrusted input. 4. Give only the selected synthetic input sections/files and the prompt below to an existing firm-approved private workspace, or perform the clerical comparison manually. Keep expected-result notes separate from the input. For planning checklists, leave unknown requirements explicit instead of inventing them. 5. Compare the draft output with the expected fixture result. A reviewer checks original evidence and all exceptions before any separately approved action. Retain the version, scope and source references with the review. INPUT RULES Map packet and document to the lawyer-approved source version. Required roles and completion vocabulary must be supplied by staff for the platform. kind is signed_pdf or completion_certificate. Artifact sha256 fingerprints refer to signed bytes; do not compare them to unsigned-source bytes. FILES - required.template.csv: Approved document/version/signer/role requirements - required.example.csv: Approved document/version/signer/role requirements - envelopes.template.csv: Explicit envelope-to-source document mapping - envelopes.example.csv: Explicit envelope-to-source document mapping - recipient_events.template.csv: Recipient-level evidence; an envelope status cannot stand in for an absent recipient - recipient_events.example.csv: Recipient-level evidence; an envelope status cannot stand in for an absent recipient - artifacts.template.csv: Downloaded signed and completion-certificate metadata - artifacts.example.csv: Downloaded signed and completion-certificate metadata COPYABLE OFFLINE PROMPT Use only these synthetic tables. Match every approved document/version/signer/role to an envelope and recipient event. Flag absent or duplicated mappings, incomplete required recipient statuses, missing signed artifacts/certificates and envelope-ID conflicts. Preserve source refs and report unknowns. An envelope marked completed does not satisfy a required signer absent from its configuration. Do not infer witness/notary requirements, authenticate identity, validate execution, resend invitations, sign, change envelopes or delete drafts. Return packet_id,document_id,signer_id,role,envelope_id,exception,evidence_refs and a lawyer-review checklist. INPUTS required.csv = packet_id,document_id,approved_source_version,signer_id,role. envelopes.csv = envelope_id,packet_id,document_id,source_version,envelope_status. recipient_events.csv = event_id,envelope_id,signer_id,role,status,event_at,source_ref. artifacts.csv = artifact_id,envelope_id,document_id,kind,sha256,source_ref where kind=signed_pdf|completion_certificate. roles/statuses are supplied platform vocabulary, not inferred legal requirements. OUTPUT A list of missing signer, role, document or certificate evidence and inconsistent envelope IDs. Signature completion does not establish engagement acceptance. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. EXPECTED SYNTHETIC FIXTURE RESULT Approved D1/v2 requires S1 signer and W1 witness. Envelope E1 maps D1/v2, status completed; only S1 has completed event. Signed PDF present, certificate absent. Expected W1 required evidence missing and E1 certificate missing, despite completed envelope. If mapping is D1/v1, also flag source-version mismatch; do not compare unsigned/signed bytes as identical. LIMITS - Lawyer determines requirements and legal sufficiency, including authority, witnessing/notarization, signature method and permitted reuse. Staff opens actual returned packet and certificate. No legal agreements accepted or signed by the workflow. - Synthetic data only in the delivered files. No credentials, real client records, live-action scripts, API connection or Make blueprint is included. - Real use requires firm-approved access, confidentiality, processing terms, retention, product access and reviewer authority. Pseudonymous IDs alone do not anonymize real records.