{
  "schema": "varexis-index-delivery/1",
  "catalog_version": "2026-10-18T16:14:30.674Z",
  "route_id": "agentic_pack_data_exit_v1",
  "question": "How can I reconcile declared data exports, deletion, retention and residual holdings offline?",
  "answer": "Reconcile declared holdings, export item coverage, deletion outcomes, retention conditions and residual copies. Checks customer-supplied versioned declarations only. No actual deletion verification, vendor-system inspection, unknown-backup discovery, legal certification or offboarding-completion assurance. Free synthetic demonstrations show actual execution of this package. Source bindings provide dated context; they do not certify the executable rules.",
  "records": [
    {
      "record_id": "VXI-EXT-PROCUREMENT-OPENSEARCH-MANUAL-SNAPSHOT-SEPARATE-EXIT-INVENTORY-01-v1",
      "url": "/varexis-index/records/opensearch-manual-snapshot-separate-exit-inventory.json",
      "content_sha256": "557585225776d52ec8bbd33abfc715c5dd122bd79da35c97c2558236403c2e22",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-18T16:14:30.674Z",
        "record_id": "VXI-EXT-PROCUREMENT-OPENSEARCH-MANUAL-SNAPSHOT-SEPARATE-EXIT-INVENTORY-01-v1",
        "record_kind": "external_reference",
        "title": "OpenSearch: Manual snapshots have separate custody",
        "system": "OpenSearch",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?",
        "near_questions": [
          "Where are manual OpenSearch snapshots stored?",
          "Does automated snapshot retention cover customer S3 backups?",
          "Which separate snapshots belong in a search-service exit checklist?",
          "What evidence accounts for manually retained search indexes?"
        ],
        "supported_claims": [
          {
            "claim": "OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Actual snapshot deletion, discovery of unknown copies or successful offboarding",
          "Buyer deployment testing, live runtime enforcement, certification or permission to act",
          "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
        ],
        "public_summary": "OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "Creating index snapshots in Amazon OpenSearch Service - Amazon OpenSearch Service",
          "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html",
          "checked_on": "2026-10-18",
          "candidate_record_id": "VXI-EXT-PROCUREMENT-OPENSEARCH-MANUAL-SNAPSHOT-SEPARATE-EXIT-INVENTORY-01-v1",
          "candidate_record_sha256": "bcbdac5c602a039633855366a193686616d33afef11294a8069561cb219129db",
          "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": "OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.",
          "required_buyer_context": "Automated and manual repository inventory. Snapshot identifiers and customer S3 ownership. Retention rules and deletion outcome references. 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": "Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?",
          "documented_statement": {
            "status": "documented",
            "statement": "OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.",
            "source_ids": [
              "opensearch-snapshot"
            ]
          },
          "buyer_evidence_required": [
            "Automated and manual repository inventory.",
            "Snapshot identifiers and customer S3 ownership.",
            "Retention rules and deletion outcome references."
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Do not close residual-data review from automated retention alone while manual snapshots remain unaccounted for."
          },
          "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": "opensearch-snapshot",
              "url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html",
              "final_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html",
              "title": "Creating index snapshots in Amazon OpenSearch Service - Amazon OpenSearch Service",
              "checked_on": "2026-10-18",
              "captured_at_utc": "2026-10-18T16:08:54.284Z",
              "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
              "sha256": "7acea2bb3d1f7a88d17fc9f60e4fbb54744cec49ff78ce7f3907344b92673425",
              "bytes": 27149,
              "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
              "reviewed_sections": [
                "Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?"
              ]
            }
          ],
          "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": "Include customer snapshot repositories in an AI search-service exit review.",
            "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": "Automated and manual repository inventory. Snapshot identifiers and customer S3 ownership. Retention rules and deletion outcome references."
          },
          "buyer_relevance": "Include customer snapshot repositories in an AI search-service exit review.",
          "refusal_conditions": [
            "Do not close residual-data review from automated retention alone while manual snapshots remain unaccounted for."
          ]
        },
        "niche": {
          "niche_id": "enterprise-ai-data-custody-exit-assurance",
          "label": "Enterprise AI Data Custody & Exit Assurance",
          "classification_id": "custody",
          "classification_label": "AI Data Custody, Retention & Exit Assurance",
          "topic_id": "custody",
          "buyer_intent": "Include customer snapshot repositories in an AI search-service exit review.",
          "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#opensearch-manual-snapshot-separate-exit-inventory",
        "machine_readable_record": "/varexis-index/records/opensearch-manual-snapshot-separate-exit-inventory.json"
      }
    },
    {
      "record_id": "VXI-EXT-PROCUREMENT-ELASTICSEARCH-SNAPSHOT-EXPORT-COVERAGE-EXCLUSIONS-01-v1",
      "url": "/varexis-index/records/elasticsearch-snapshot-export-coverage-exclusions.json",
      "content_sha256": "1d0c40487a8d90a8f4b40286ec5a18e56d8b005898cc3c64184496f381bf7dd4",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-18T16:14:30.674Z",
        "record_id": "VXI-EXT-PROCUREMENT-ELASTICSEARCH-SNAPSHOT-EXPORT-COVERAGE-EXCLUSIONS-01-v1",
        "record_kind": "external_reference",
        "title": "Elasticsearch: Snapshot success is not a full environment export",
        "system": "Elasticsearch",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?",
        "near_questions": [
          "Are closed Elasticsearch indices included in snapshots?",
          "Does a snapshot include node configuration files?",
          "Which feature states must be included in an exit export?",
          "Can snapshot success establish complete migration coverage?"
        ],
        "supported_claims": [
          {
            "claim": "Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Restorability in the buyer environment, deletion or completeness of unknown holdings",
          "Buyer deployment testing, live runtime enforcement, certification or permission to act",
          "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
        ],
        "public_summary": "Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "Snapshot and restore in Elasticsearch | Elastic Docs",
          "source_url": "https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore",
          "checked_on": "2026-10-18",
          "candidate_record_id": "VXI-EXT-PROCUREMENT-ELASTICSEARCH-SNAPSHOT-EXPORT-COVERAGE-EXCLUSIONS-01-v1",
          "candidate_record_sha256": "d82465501cada562ae83ef7c8ef949c270873f441c976055a37bf26aba908ff0",
          "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": "Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.",
          "required_buyer_context": "Index open/closed state and selected scope. Feature states and snapshot manifest. Excluded configuration inventory and restore compatibility. 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 an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?",
          "documented_statement": {
            "status": "documented",
            "statement": "Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.",
            "source_ids": [
              "elastic-snapshot"
            ]
          },
          "buyer_evidence_required": [
            "Index open/closed state and selected scope.",
            "Feature states and snapshot manifest.",
            "Excluded configuration inventory and restore compatibility."
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Do not declare export completeness without reconciling excluded indices and configuration."
          },
          "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": "elastic-snapshot",
              "url": "https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore",
              "final_url": "https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore",
              "title": "Snapshot and restore in Elasticsearch | Elastic Docs",
              "checked_on": "2026-10-18",
              "captured_at_utc": "2026-10-18T16:08:54.679Z",
              "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
              "sha256": "b601ff02eb62396ae2529d1869750975936b1b8a538f346db7acc5d0cd3db9db",
              "bytes": 310022,
              "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
              "reviewed_sections": [
                "Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?"
              ]
            }
          ],
          "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": "Reconcile the export against data and configuration needed for a controlled exit.",
            "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": "Index open/closed state and selected scope. Feature states and snapshot manifest. Excluded configuration inventory and restore compatibility."
          },
          "buyer_relevance": "Reconcile the export against data and configuration needed for a controlled exit.",
          "refusal_conditions": [
            "Do not declare export completeness without reconciling excluded indices and configuration."
          ]
        },
        "niche": {
          "niche_id": "enterprise-ai-data-custody-exit-assurance",
          "label": "Enterprise AI Data Custody & Exit Assurance",
          "classification_id": "custody",
          "classification_label": "AI Data Custody, Retention & Exit Assurance",
          "topic_id": "custody",
          "buyer_intent": "Reconcile the export against data and configuration needed for a controlled exit.",
          "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#elasticsearch-snapshot-export-coverage-exclusions",
        "machine_readable_record": "/varexis-index/records/elasticsearch-snapshot-export-coverage-exclusions.json"
      }
    },
    {
      "record_id": "VXI-EXT-PROCUREMENT-QDRANT-DISTRIBUTED-SNAPSHOT-NODE-COVERAGE-01-v1",
      "url": "/varexis-index/records/qdrant-distributed-snapshot-node-coverage.json",
      "content_sha256": "401c0db2c1aafe619e3decdd0f39ee610ff977c71779750ad9d7ebf57a6ec6d4",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-18T16:14:30.674Z",
        "record_id": "VXI-EXT-PROCUREMENT-QDRANT-DISTRIBUTED-SNAPSHOT-NODE-COVERAGE-01-v1",
        "record_kind": "external_reference",
        "title": "Qdrant: A distributed export needs node coverage",
        "system": "Qdrant",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Does one Qdrant node snapshot establish a complete distributed collection export?",
        "near_questions": [
          "Which nodes need snapshots for a distributed Qdrant export?",
          "Does wait=false return a completed snapshot artifact?",
          "How should background Qdrant snapshot creation be reconciled?",
          "What connects downloaded snapshots to the collection topology?"
        ],
        "supported_claims": [
          {
            "claim": "Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Actual customer export, point-in-time consistency across nodes or successful restoration",
          "Buyer deployment testing, live runtime enforcement, certification or permission to act",
          "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
        ],
        "public_summary": "Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "Snapshots - Qdrant",
          "source_url": "https://qdrant.tech/documentation/tutorials-operations/create-snapshot/",
          "checked_on": "2026-10-18",
          "candidate_record_id": "VXI-EXT-PROCUREMENT-QDRANT-DISTRIBUTED-SNAPSHOT-NODE-COVERAGE-01-v1",
          "candidate_record_sha256": "707db166b029614227c5709a52763495e06120a5916bc745265942338234009d",
          "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": "Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.",
          "required_buyer_context": "Cluster node and shard layout. Per-node snapshot completion and names. Downloaded artifacts, hashes and restore plan. 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 one Qdrant node snapshot establish a complete distributed collection export?",
          "documented_statement": {
            "status": "documented",
            "statement": "Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.",
            "source_ids": [
              "qdrant-snapshot"
            ]
          },
          "buyer_evidence_required": [
            "Cluster node and shard layout.",
            "Per-node snapshot completion and names.",
            "Downloaded artifacts, hashes and restore plan."
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Do not mark the distributed export complete while node snapshots or background results remain unresolved."
          },
          "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": "qdrant-snapshot",
              "url": "https://qdrant.tech/documentation/tutorials-operations/create-snapshot/",
              "final_url": "https://qdrant.tech/documentation/tutorials-operations/create-snapshot/",
              "title": "Snapshots - Qdrant",
              "checked_on": "2026-10-18",
              "captured_at_utc": "2026-10-18T16:09:55.636Z",
              "version_context": "Official rolling documentation captured on 2026-10-18",
              "sha256": "2fec7981f67e8d8e688bd4076102d0b1d54c075a2f9380bf3d24ae4b23ff117a",
              "bytes": 98579,
              "hash_basis": "Decoded HTTP response body bytes; capture identity only, not independent truth.",
              "reviewed_sections": [
                "Does one Qdrant node snapshot establish a complete distributed collection export?"
              ]
            }
          ],
          "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": "Reconcile vector-store exit artifacts against the distributed collection layout.",
            "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": "Cluster node and shard layout. Per-node snapshot completion and names. Downloaded artifacts, hashes and restore plan."
          },
          "buyer_relevance": "Reconcile vector-store exit artifacts against the distributed collection layout.",
          "refusal_conditions": [
            "Do not mark the distributed export complete while node snapshots or background results remain unresolved."
          ]
        },
        "niche": {
          "niche_id": "enterprise-ai-data-custody-exit-assurance",
          "label": "Enterprise AI Data Custody & Exit Assurance",
          "classification_id": "custody",
          "classification_label": "AI Data Custody, Retention & Exit Assurance",
          "topic_id": "custody",
          "buyer_intent": "Reconcile vector-store exit artifacts against the distributed collection layout.",
          "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#qdrant-distributed-snapshot-node-coverage",
        "machine_readable_record": "/varexis-index/records/qdrant-distributed-snapshot-node-coverage.json"
      }
    }
  ],
  "basis": "VAREXIS-authored offline reconciliation rules, synthetic fixtures and bound public documentation reviews. No fresh source review, customer deployment test, artifact authentication or real-world event verification is performed.",
  "boundary": "One-time GBP 79 plus applicable VAT for the versioned offline executable and one-buyer internal-use licence. Independent entitlement required; not included in GBP 5/19 offers or any existing subscription. No updates, monitoring, redistribution, hosted resale or support SLA. No actual deletion verification, vendor-system inspection, unknown-backup discovery, legal certification or offboarding-completion assurance.",
  "pack": {
    "schema": "varexis-index-evidence-pack/1",
    "pack_id": "agent-data-exit",
    "version": "1.0.0",
    "title": "Agent Data Exit & Retention Reconciler",
    "prepared_at_utc": "2026-10-18T16:45:17.999Z",
    "review_status": "documentation_review_only",
    "source_checked_on": [
      "2026-10-18"
    ],
    "source_capture_date": null,
    "source_capture_boundary": "Each source record retains its own capture date, version and hash. Executable rules are VAREXIS-authored; source documentation is context, not vendor validation.",
    "summary_markdown": "Reconcile declared holdings, export item coverage, deletion outcomes, retention conditions and residual copies. Checks customer-supplied versioned declarations only. No actual deletion verification, vendor-system inspection, unknown-backup discovery, legal certification or offboarding-completion assurance. Free synthetic demonstrations show actual execution of this package. Source bindings provide dated context; they do not certify the executable rules.\n\nOne-time GBP 79 plus applicable VAT for the versioned offline executable and one-buyer internal-use licence. Independent entitlement required; not included in GBP 5/19 offers or any existing subscription. No updates, monitoring, redistribution, hosted resale or support SLA. No actual deletion verification, vendor-system inspection, unknown-backup discovery, legal certification or offboarding-completion assurance.",
    "comparison": [
      {
        "record_id": "VXI-EXT-PROCUREMENT-OPENSEARCH-MANUAL-SNAPSHOT-SEPARATE-EXIT-INVENTORY-01-v1",
        "subject": "OpenSearch",
        "review_status": "documentation_review_only",
        "checked_on": "2026-10-18",
        "claim_to_check": "Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?",
        "documented_statement": {
          "status": "documented",
          "statement": "OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.",
          "source_ids": [
            "opensearch-snapshot"
          ]
        },
        "buyer_evidence_required": [
          "Automated and manual repository inventory.",
          "Snapshot identifiers and customer S3 ownership.",
          "Retention rules and deletion outcome references."
        ],
        "review_condition": {
          "status": "varexis_review_policy",
          "statement": "Do not close residual-data review from automated retention alone while manual snapshots remain unaccounted for."
        },
        "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."
      },
      {
        "record_id": "VXI-EXT-PROCUREMENT-ELASTICSEARCH-SNAPSHOT-EXPORT-COVERAGE-EXCLUSIONS-01-v1",
        "subject": "Elasticsearch",
        "review_status": "documentation_review_only",
        "checked_on": "2026-10-18",
        "claim_to_check": "Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?",
        "documented_statement": {
          "status": "documented",
          "statement": "Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.",
          "source_ids": [
            "elastic-snapshot"
          ]
        },
        "buyer_evidence_required": [
          "Index open/closed state and selected scope.",
          "Feature states and snapshot manifest.",
          "Excluded configuration inventory and restore compatibility."
        ],
        "review_condition": {
          "status": "varexis_review_policy",
          "statement": "Do not declare export completeness without reconciling excluded indices and configuration."
        },
        "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."
      },
      {
        "record_id": "VXI-EXT-PROCUREMENT-QDRANT-DISTRIBUTED-SNAPSHOT-NODE-COVERAGE-01-v1",
        "subject": "Qdrant",
        "review_status": "documentation_review_only",
        "checked_on": "2026-10-18",
        "claim_to_check": "Does one Qdrant node snapshot establish a complete distributed collection export?",
        "documented_statement": {
          "status": "documented",
          "statement": "Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.",
          "source_ids": [
            "qdrant-snapshot"
          ]
        },
        "buyer_evidence_required": [
          "Cluster node and shard layout.",
          "Per-node snapshot completion and names.",
          "Downloaded artifacts, hashes and restore plan."
        ],
        "review_condition": {
          "status": "varexis_review_policy",
          "statement": "Do not mark the distributed export complete while node snapshots or background results remain unresolved."
        },
        "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."
      }
    ],
    "members": [
      {
        "schema": "varexis-index-delivery/1",
        "catalog_version": "2026-10-18T16:14:30.674Z",
        "route_id": "agentic_reviewed_opensearch_manual_snapshot_separate_exit_inventory",
        "question": "Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?",
        "answer": "OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.",
        "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.",
        "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.",
        "snapshot_sha256": "577f466876c40d311e1ccfdb276c549bc402dc55d27b906b60f6d6f9596515b0",
        "record_ids": [
          "VXI-EXT-PROCUREMENT-OPENSEARCH-MANUAL-SNAPSHOT-SEPARATE-EXIT-INVENTORY-01-v1"
        ]
      },
      {
        "schema": "varexis-index-delivery/1",
        "catalog_version": "2026-10-18T16:14:30.674Z",
        "route_id": "agentic_reviewed_elasticsearch_snapshot_export_coverage_exclusions",
        "question": "Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?",
        "answer": "Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.",
        "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.",
        "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.",
        "snapshot_sha256": "0d535c14c6f6136e2c859773480e53210c87ddc1bd143a68348a866ce56361ba",
        "record_ids": [
          "VXI-EXT-PROCUREMENT-ELASTICSEARCH-SNAPSHOT-EXPORT-COVERAGE-EXCLUSIONS-01-v1"
        ]
      },
      {
        "schema": "varexis-index-delivery/1",
        "catalog_version": "2026-10-18T16:14:30.674Z",
        "route_id": "agentic_reviewed_qdrant_distributed_snapshot_node_coverage",
        "question": "Does one Qdrant node snapshot establish a complete distributed collection export?",
        "answer": "Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.",
        "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.",
        "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.",
        "snapshot_sha256": "5bc6ca8102ae9bb8192eea9a89a2691c56960e8234217a76e43acf4bebcda75b",
        "record_ids": [
          "VXI-EXT-PROCUREMENT-QDRANT-DISTRIBUTED-SNAPSHOT-NODE-COVERAGE-01-v1"
        ]
      }
    ],
    "rights_review": {
      "reviewed_on": "2026-10-18",
      "scope": "Original VAREXIS rules and synthetic examples with existing attributed public review summaries.",
      "included": "Original executable, schemas and synthetic fixtures; public review records with original hashes.",
      "excluded": "Upstream document bodies/code, credentials, personal data and protected research.",
      "redistribution_boundary": "Source URLs identify context and do not grant redistribution rights. The executable is separately licensed for internal use.",
      "terms_url": "https://varexis.tech/checkout-terms",
      "independent_testing": false
    },
    "delivery_unit": {
      "kind": "one_licensed_product",
      "member_count": 3,
      "developer_query_units": 0,
      "research_query_units": 0,
      "extra_member_purchases": false,
      "automatic_refresh": false,
      "service_id": "data_exit",
      "existing_subscriptions_eligible": false
    }
  },
  "paid_artifact": {
    "schema": "varexis-paid-artifact/1",
    "filename": "varexis-agent-data-exit-v1.zip",
    "media_type": "application/zip",
    "encoding": "base64",
    "archive_sha256": "88127f67d633f2472da61838affd69e4826b42509cc77858e748797d5bdb33c4",
    "manifest_sha256": "3ea0ed0b4c420febf662a2fea5cd53db79e1f435c16b5207de1ec97e692df4a8",
    "bytes": 22172,
    "runtime": "Node.js 24",
    "licence": "VAREXIS Agent Data Exit & Retention Reconciler v1.0.0\nOne-time licence for one purchasing individual or one legal entity, including its staff and agents acting internally on its behalf. Reusable local execution and internal CI use; no per-run fee. No sublicensing, redistribution of executable/rules, hosted customer service, API resale or external agent distribution. Each other executable requires its own licence. Existing subscriptions and GBP 5/19 offers do not include this product. Public evidence retains its existing terms. No updates, monitoring, deployment assurance, certification or support SLA is included. Billing and delivery support follows https://varexis.tech/checkout-terms. Statutory rights are unaffected.\nLicence rights begin after provider-verified payment for this product. Retain the original purchase key for authenticated delivery and recovery.\n",
    "extract_and_run": "Verify ZIP SHA-256 against authenticated delivery. Extract, then run evaluate.mjs with this externally supplied manifest_sha256 and a schema-valid JSON declaration. No uploads or network calls."
  },
  "snapshot_sha256": "a3d35a24b9005d3023b329fb62ac2e9500b52512e21f817ff053f07984865276",
  "preview_kind": "paid_executable_manifest",
  "preview_payload_sha256": "466be1a80f6ae2de885b158052a81ca18a9409e807d11e324240d50851b4414c"
}