{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T10:49:29.433Z",
  "record_id": "VXI-EXT-PROCUREMENT-SLACK-EVENT-RETRY-IDENTITY-01-v1",
  "record_kind": "external_reference",
  "title": "Slack Events: Retry delivery is not a new event",
  "system": "Slack Events API",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Should each Slack Events API delivery trigger a fresh agent action?",
  "near_questions": [
    "What event_id was received?",
    "Did the receiver acknowledge in time?",
    "Is this a retry of the same event?",
    "Are delayed events enabled?",
    "Was the original action completed?",
    "Does the app store processing outcomes?",
    "Could acknowledgement fail after action success?",
    "Which retry metadata was captured?",
    "Can repeated delivery duplicate a message?",
    "What is the recovery policy?",
    "Are event and attempt counts separated?",
    "Can I retain the Slack retry review?"
  ],
  "supported_claims": [
    {
      "claim": "Slack assigns a globally unique event_id and retries failed delivery acknowledgements. Optional delayed events settings extend retry handling. Receipt attempts and logical events are different, so an integration should preserve event identity when deciding whether to act again.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Slack assigns a globally unique event_id and retries failed delivery acknowledgements. Optional delayed events settings extend retry handling. Receipt attempts and logical events are different, so an integration should preserve event identity when deciding whether to act again.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Slack: Events API",
    "source_url": "https://docs.slack.dev/apis/events-api/",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SLACK-EVENT-RETRY-IDENTITY-01-v1",
    "candidate_record_sha256": "39458b5ce8198e58605aa0ca5aa4819cc6618400a9525c4488f5c387fcb15328",
    "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": "Slack assigns a globally unique event_id and retries failed delivery acknowledgements. Optional delayed events settings extend retry handling. Receipt attempts and logical events are different, so an integration should preserve event identity when deciding whether to act again.",
    "required_buyer_context": "Event identity, acknowledgement timing, retry settings and processing state. Effective buyer configuration and operational results were 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-17",
    "claim_to_check": "Should each Slack Events API delivery trigger a fresh agent action?",
    "documented_statement": {
      "status": "documented",
      "statement": "Slack assigns a globally unique event_id and retries failed delivery acknowledgements. Optional delayed events settings extend retry handling. Receipt attempts and logical events are different, so an integration should preserve event identity when deciding whether to act again.",
      "source_ids": [
        "slack-events"
      ]
    },
    "buyer_evidence_required": [
      "event_id and received retry metadata.",
      "Acknowledgement and delayed-event configuration.",
      "Durable processing outcome for the logical event."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Review acknowledgement and action completion separately; do not equate each delivery attempt with a new instruction."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "slack-events",
        "url": "https://docs.slack.dev/apis/events-api/",
        "final_url": "https://docs.slack.dev/apis/events-api/",
        "title": "Slack: Events API",
        "checked_on": "2026-10-17",
        "sha256": "ac2c042a92142090e6bb7dfd76f30574a78dfe509e28191d026ae539e8ee4f48",
        "bytes": 155384
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Should each Slack Events API delivery trigger a fresh agent action?",
      "free": "Complete review, practical questions, sources 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": "Event identity, acknowledgement timing, retry settings and processing state."
    }
  },
  "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#slack-event-retries-event-id-not-new-action",
  "machine_readable_record": "/varexis-index/records/slack-event-retries-event-id-not-new-action.json"
}