{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T19:34:16.969Z",
  "record_id": "VXI-EXT-PROCUREMENT-DOCUSIGN-COMPLETION-EVENT-DOCUMENT-PROCESSING-EVIDENCE-01-v1",
  "record_kind": "external_reference",
  "title": "Docusign: Completion events and retained signed-document evidence",
  "system": "Docusign",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Docusign completion notification prove which signed document was retained and processed downstream?",
  "near_questions": [
    "Does every Docusign completion webhook contain the signed document?",
    "Which Docusign completion evidence should be retained with an envelope?",
    "Does accepting a Docusign webhook prove downstream processing completed?",
    "How should a signed-document copy be tied to its Docusign completion event?"
  ],
  "supported_claims": [
    {
      "claim": "Docusign recommends configuring completed documents, completion certificates where needed and document fields in completion webhooks. It also recommends accepting received messages into a queue for asynchronous processing. Document inclusion is configurable; a completion event and the listener's later processing are separate parts of the documented integration.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Signature validation, legal validity or observed downstream processing",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Docusign recommends configuring completed documents, completion certificates where needed and document fields in completion webhooks. It also recommends accepting received messages into a queue for asynchronous processing. Document inclusion is configurable; a completion event and the listener's later processing are separate parts of the documented integration.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Best practices for building your listener | Docusign",
    "source_url": "https://developers.docusign.com/platform/webhooks/connect/build-listener/",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DOCUSIGN-COMPLETION-EVENT-DOCUMENT-PROCESSING-EVIDENCE-01-v1",
    "candidate_record_sha256": "a55cd4fd8dd8e9e493d991689b81973317c8bdd020b0c5e35ff3cfd1f644ebd7",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Docusign recommends configuring completed documents, completion certificates where needed and document fields in completion webhooks. It also recommends accepting received messages into a queue for asynchronous processing. Document inclusion is configurable; a completion event and the listener's later processing are separate parts of the documented integration.",
    "required_buyer_context": "Envelope and account identity, event type and document-inclusion settings. Retrieved signed bytes, document identifiers and retained content hashes. Queue receipt and downstream processing outcome bound to that document. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-18",
    "claim_to_check": "Does a Docusign completion notification prove which signed document was retained and processed downstream?",
    "documented_statement": {
      "status": "documented",
      "statement": "Docusign recommends configuring completed documents, completion certificates where needed and document fields in completion webhooks. It also recommends accepting received messages into a queue for asynchronous processing. Document inclusion is configurable; a completion event and the listener's later processing are separate parts of the documented integration.",
      "source_ids": [
        "docusign-listener-data"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Identifying the exact retained document and completed processing requires evidence beyond the completion notification.",
      "source_ids": [
        "docusign-listener-data"
      ]
    },
    "buyer_evidence_required": [
      "Envelope and account identity, event type and document-inclusion settings.",
      "Retrieved signed bytes, document identifiers and retained content hashes.",
      "Queue receipt and downstream processing outcome bound to that document."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse completed-document-processing claims when signed bytes or processing receipts cannot be bound to the event."
    },
    "unknowns": "No envelope, signature validity or listener processing was independently verified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No envelope, signature validity or listener processing was independently verified."
    },
    "evidence_sources": [
      {
        "source_id": "docusign-listener-data",
        "url": "https://developers.docusign.com/platform/webhooks/connect/build-listener/",
        "final_url": "https://developers.docusign.com/page-data/platform/webhooks/connect/build-listener/page-data.json",
        "title": "Best practices for building your listener | Docusign",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T19:25:25.079Z",
        "version_context": "Rolling Connect listener guide; publisher Gatsby page-data JSON supplies the article body absent from the HTML shell.",
        "sha256": "f03d1d906b2b1a2f9307c18d16f6ed07dc216d016491cb1d55df3bae16bf13ea",
        "bytes": 59807,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Best practices for building your listener: document inclusion and asynchronous processing"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "capture_url": "https://developers.docusign.com/page-data/platform/webhooks/connect/build-listener/page-data.json"
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.",
    "paid_value": {
      "decision_context": "Bind an action request to the outcome evidence needed for a business decision.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck Connect payload settings, document retrieval and asynchronous listener behavior."
    },
    "buyer_relevance": "Bind an action request to the outcome evidence needed for a business decision.",
    "refusal_conditions": [
      "Refuse completed-document-processing claims when signed bytes or processing receipts cannot be bound to the event."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Bind an action request to the outcome evidence needed for a business decision.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#docusign-completion-event-document-processing-evidence",
  "machine_readable_record": "/varexis-index/records/docusign-completion-event-document-processing-evidence.json"
}
