{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-29T22:28:47.410696+00:00",
  "record_id": "VXI-EXT-ICE07-PUBSUB-DEADLETTER-ATTEMPT-COUNT-APPROXIMATE-01-v1",
  "record_kind": "external_reference",
  "title": "Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling",
  "system": "Google Cloud",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling?",
  "near_questions": [
    "Can delivery exceed maxDeliveryAttempts?",
    "Are dead-letter retry counts exact?",
    "Why can attempt counts reset?",
    "Does the policy enforce a business-action limit?"
  ],
  "supported_claims": [
    {
      "claim": "Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Do not treat the setting as a hard execution cap. Check actual attempts and operation-level idempotency.",
    "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Dead-letter topics  |  Pub/Sub  |  Google Cloud Documentation",
    "source_url": "https://docs.cloud.google.com/pubsub/docs/dead-letter-topics",
    "checked_on": "2026-10-29",
    "candidate_record_id": "VXI-EXT-ICE07-PUBSUB-DEADLETTER-ATTEMPT-COUNT-APPROXIMATE-01-v1",
    "candidate_record_sha256": "ed33cdda896752a130d8645c21ab2b3199fd4df5ad18c96a69587f7f2405d60d",
    "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": "Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.",
    "required_buyer_context": "subscription configuration; service-account IAM; delivery attempts; operation results. 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-29",
    "claim_to_check": "Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling?",
    "documented_statement": {
      "status": "documented",
      "statement": "Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.",
      "source_ids": [
        "pubsub-deadletter"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Assess whether a retry policy bounds repeated external actions. Require the missing evidence before accepting, retrying or closing the operation. Dead-letter attempt accounting differs from exactly-once acknowledgement scope. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "pubsub-deadletter"
      ]
    },
    "buyer_evidence_required": [
      "subscription configuration",
      "service-account IAM",
      "delivery attempts",
      "operation results"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not treat the setting as a hard execution cap. Check actual attempts and operation-level idempotency."
    },
    "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer deployment or transaction was observed."
    },
    "evidence_sources": [
      {
        "source_id": "pubsub-deadletter",
        "url": "https://docs.cloud.google.com/pubsub/docs/dead-letter-topics",
        "final_url": "https://docs.cloud.google.com/pubsub/docs/dead-letter-topics",
        "captured_at_utc": "2026-10-29T22:17:23.990983+00:00",
        "status": 200,
        "content_type": "text/html; charset=utf-8",
        "bytes": 663763,
        "sha256": "62302eceb2608c1c26384fc97bb595e75cd2d227044887067fce8b131e3118b1",
        "publisher": "Google Cloud",
        "title": "Dead-letter topics  |  Pub/Sub  |  Google Cloud Documentation",
        "version_context": "Rolling official documentation snapshot; consult current service and client version before reliance",
        "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights retained; no trademark or code licence conveyed.",
        "checked_on": "2026-10-29",
        "capture_status": 200,
        "claim_review_completed": true,
        "hash_basis": "SHA-256 of captured HTTP response body bytes",
        "reviewed_sections": [
          "How maximum delivery attempts are calculated",
          "How dead-letter topics work"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
    "paid_value": {
      "decision_context": "Assess whether a retry policy bounds repeated external actions. Require the missing evidence before accepting, retrying or closing the operation.",
      "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
      "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
      "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
      "excluded": [
        "Fresh source research",
        "Native provider integration or schema support",
        "Live inspection or runtime enforcement",
        "Payment settlement or verified deletion",
        "Certification or expanded licences"
      ],
      "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
      "specific_watch": "How maximum delivery attempts are calculated"
    },
    "buyer_relevance": "Assess whether a retry policy bounds repeated external actions. Require the missing evidence before accepting, retrying or closing the operation.",
    "refusal_conditions": [
      "Do not treat the setting as a hard execution cap. Check actual attempts and operation-level idempotency.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "Workflow operator or incident reviewer",
      "scenario": "Assess whether a retry policy bounds repeated external actions.",
      "consequence": "Require the missing evidence before accepting, retrying or closing the operation.",
      "confidence": "High for captured documentation; buyer applicability and deployed behaviour unverified."
    },
    "novelty_review": {
      "candidate_id": "ICE07-014",
      "disposition": "EXTENSION",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-PUBSUB-EXACTLY-ONCE-01-v1",
      "nearest_record_url": "/varexis-index/records/pubsub-exactly-once-ack-region-boundary.json",
      "nearest_record_sha256": "a58b6c55354da432917eefe2c3f584ff0bbd3bfb6c498c34f98bb75ac015decd",
      "material_distinction": "Dead-letter attempt accounting differs from exactly-once acknowledgement scope.",
      "review_status": "PASS: implementing-agent source and duplication review"
    },
    "optional_selection": {
      "guide_id": "workflow-completion-recovery",
      "guide_url": "/index-guides/workflow-completion-recovery",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "checker": {
        "product_id": "agent-audit-coverage",
        "price_gbp_excluding_vat": 79,
        "purchase_url": "/index-access?route=agentic_pack_audit_coverage_v1",
        "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
        "benefit": "Optional local analysis of supported supplied declarations only; no native provider integration or verification is added."
      },
      "boundary": "Optional Audit Coverage only reconciles supported declared event chains and completeness. It does not connect to these services, verify signatures, inspect queues, execute recovery or approve software."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-ICE07-PUBSUB-DEADLETTER-ATTEMPT-COUNT-APPROXIMATE-01-v1"
      },
      "record_url": "/varexis-index/records/pubsub-deadletter-attempt-count-approximate.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "ice07-audit",
    "label": "Audit, Provenance & Evidence Accountability",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Assess whether a retry policy bounds repeated external actions. Require the missing evidence before accepting, retrying or closing the operation.",
    "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#pubsub-deadletter-attempt-count-approximate",
  "machine_readable_record": "/varexis-index/records/pubsub-deadletter-attempt-count-approximate.json"
}
