{
  "id": "memory-custody",
  "product_id": "memory-custody-operator",
  "service_id": "memory_custody_operator_pack",
  "route_id": "agentic_operator_memory_custody_v1",
  "title": "Agent Memory & Context Custody",
  "description": "Memory can persist as transcripts, extracted facts, vectors and backups after an agent is disconnected. This operator pack helps a data owner reconcile supplied identity, consent, retention and exit evidence before making a scoped assertion. Receive editable custody worksheets, refusal criteria and a completed synthetic example that tracks unresolved copies. It does not inspect platforms or verify deletion.",
  "inputs": "Supplied memory/store inventory, tenant/user/agent mappings, use basis, retention/deletion receipts, derived-copy and background-job evidence.",
  "outputs": "A completed custody/exit decision record, residual-copy register and evidence gaps, with narrower supported conclusions.",
  "limitations": "No live inspection, discovery of unknown copies, actual deletion verification, legal assessment, certification or automated analysis.",
  "demonstration": "REFUSE_CLAIM: a supplied synthetic local-file removal receipt does not establish all memory deleted while managed facts, a backup and a background job remain unresolved.",
  "version": "1.0.0",
  "prepared_at_utc": "2026-10-30T18:53:33.881Z",
  "net_amount": 1900,
  "currency": "gbp",
  "billing": "one_time",
  "tax_behavior": "exclusive",
  "price_gbp_excluding_vat": 19,
  "status": "CAPABILITIES_GATED",
  "purchase_url": "/index-access?route=agentic_operator_memory_custody_v1",
  "manifest_url": "/varexis-index/operator-packs/memory-custody.json",
  "existing_subscription_eligible": false,
  "saved_evidence_offer_eligible": false,
  "availability_source": "/api/index/capabilities",
  "availability_key": "operator_packs.agentic_operator_memory_custody_v1.enabled",
  "schema": "varexis-operator-product/1",
  "activation": "Current purchase availability is reported by operator_packs in /api/index/capabilities and controlled independently for each pack. Historical release approval or preview publication does not establish current availability.",
  "free": "Complete supporting source evidence, references, scope, file inventory and concise demonstration remain free.",
  "paid": "Editable operational templates, source-linked decision criteria, complete synthetic worked files and internal-use licence in the exact ZIP.",
  "licence": "VAREXIS Agent Memory & Context Custody Operator Pack v1.0.0\r\nOne-time internal-use licence for one purchasing individual or one legal entity, including staff and agents acting internally on its behalf. The purchaser may copy, complete and adapt these VAREXIS-authored review templates for internal decisions without a per-use fee. Completed internal decision records may be shared with the purchaser’s own reviewers and auditors for that decision; this does not grant redistribution or resale of the reusable template library. No sublicensing, template redistribution, hosted customer service, API resale, external agent distribution, executable checker licence, future updates, monitoring or support SLA is included. Public source evidence retains its existing terms; this licence does not relicense third-party documentation. Billing and delivery support follows https://varexis.tech/checkout-terms. Statutory rights are unaffected. Rights begin only after provider-verified payment for this exact product. Retain the original purchase key for authenticated delivery and recovery.\r\n",
  "archive": {
    "filename": "varexis-memory-custody-operator-v1.zip",
    "sha256": "81e75c3469260e6bd33feeaeb5a4744df3ae901d85341327c23e0317bd33f3c1",
    "bytes": 16736,
    "manifest_sha256": "58d050c0db2fe9a8d1df3eb5ee3648e18e15af245cb10214943fa6f2d30a2436",
    "file_hashes": {
      "LICENCE.txt": "a919336ac9edee91aa223d61bd8d41a3f453e52f05f2b69c25419d68e3ca49f7",
      "README.md": "fb2265dd8573f89c21bd55eb1595b675c54105e417056af2d8b2f71724c56783",
      "criteria-sources.json": "91c509a8e68d8b5f0e510904262413037cc1fe9b8385421be7e6eda184a380eb",
      "decision-criteria.md": "d6144d3c8bf841f4a392d7956d5ba2afef88cd84bfcb8c8a101bb06e4af78463",
      "example/completed-decision.json": "a8612ed882698f3c062acd14f606cacf3cfbb60205bc89114c30c7d87c1eac8e",
      "example/completed-inventory.csv": "6bc1ae31a840b5208e08df574bf8631abb9fb55d4fd4b9510d4b77dc1b528751",
      "example/completed-lifecycle.csv": "5d481737752efba03b11f1ecdb6a1f2588dcf9f603c4eb48e66f5ebe7b03c174",
      "example/completed-provenance.csv": "2686ff4875e7295c7483b9ec7fa66f0818bbde0f8d432fa17321f8934ead2e98",
      "example/completed-residual-copies.csv": "e37ebe38b7b477ce057509f76ac47b361326ec8bfdf1cf1c3494d790153b599d",
      "example/completed-retrieval-boundaries.csv": "c9b1795fd4ae67f7bdd9de5a5b81897f858fdeb3e29da63e43b2e3719d53a83d",
      "example/scenario.md": "b04ad159718724b16c071d100fcb8e750f30f5bf59d5dd47b9d5c9101e63da50",
      "example/synthetic-evidence.json": "6c52eb320e1f6256d19fe54be6c55287d75e8c9c3f4e3828b23ead6c0cdc5efa",
      "pack-contract.json": "120325aedc0f34a5adeeabc2b8de42fb47cbc2dbeef2fbbe0449780292354bf6",
      "sources.json": "e85f9cdc7a2067a31b3b5a26663cad74f827cc3b30fd9c3d4c3c21121308b3e2",
      "templates/decision-record.json": "0bc708b6dd5a45959a8599fadaeb19687795f4339ebf1867f5f332f900879a07",
      "templates/inventory.csv": "34b0f26e8de46a78ca2cbfe3497615ce9abf5ec2ae67b13eb19bfdf39272dcdf",
      "templates/lifecycle.csv": "c1d6c97a28279e47daaf383f4f8c01bf1c7430bc300e92996deab81d1da31875",
      "templates/provenance.csv": "239d5ff638fa130cd5a3bc0ab4ba1858796491f3f584b9a6176c7080a6984861",
      "templates/residual-copies.csv": "84f2a0ea3c8e2721655413d85e009175b4d2633c1c1cc62e9708f1adba2fa001",
      "templates/retrieval-boundaries.csv": "44d43d30787128cefd91f3dd8206035da0f8128137686b0ae007124efa032380"
    }
  },
  "preview": {
    "schema": "varexis-index-delivery/1",
    "catalog_version": "2026-10-30T18:53:33.881Z",
    "route_id": "agentic_operator_memory_custody_v1",
    "question": "Agent Memory & Context Custody — reusable manual operator pack",
    "answer": "Memory can persist as transcripts, extracted facts, vectors and backups after an agent is disconnected. This operator pack helps a data owner reconcile supplied identity, consent, retention and exit evidence before making a scoped assertion. Receive editable custody worksheets, refusal criteria and a completed synthetic example that tracks unresolved copies. It does not inspect platforms or verify deletion.",
    "records": [
      {
        "record_id": "VXI-EXT-ICE10-AGENTCORE-NORMALIZED-NAMESPACE-IAM-01-v1",
        "url": "/varexis-index/records/agentcore-normalized-namespace-iam.json",
        "content_sha256": "76dbab4892bfe57c17184b004a61450f8b9cd33c294f560841e33a58cdb07598",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-AGENTCORE-NORMALIZED-NAMESPACE-IAM-01-v1",
          "record_kind": "external_reference",
          "title": "Normalised namespace string controls whether IAM conditions match",
          "system": "Amazon Web Services",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Can an AgentCore namespace IAM condition omit its leading or trailing slash?",
          "near_questions": [
            "Can normalized AgentCore namespace paths differ from supplied paths?",
            "How do namespace slashes affect AgentCore IAM matching?",
            "Which namespace representation should an AgentCore access review compare?",
            "Can a raw AgentCore namespace label establish an effective IAM boundary?"
          ],
          "supported_claims": [
            {
              "claim": "AgentCore normalises namespaces with leading and trailing slashes. The guide says an IAM condition lacking these does not match the namespace on which the service acts.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.",
            "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": "AgentCore normalises namespaces with leading and trailing slashes. The guide says an IAM condition lacking these does not match the namespace on which the service acts.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Amazon Web Services primary documentation: aws memory namespaces",
            "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-AGENTCORE-NORMALIZED-NAMESPACE-IAM-01-v1",
            "candidate_record_sha256": "c012b33bbdb591b7695330a548d3a89d344345cc8b9d273d5397836dd14a8ee3",
            "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": "AgentCore normalises namespaces with leading and trailing slashes. The guide says an IAM condition lacking these does not match the namespace on which the service acts.",
            "required_buyer_context": "normalised namespace; request value; IAM condition; strategy template; denied/allowed test evidence. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Can an AgentCore namespace IAM condition omit its leading or trailing slash?",
            "documented_statement": {
              "status": "documented",
              "statement": "AgentCore normalises namespaces with leading and trailing slashes. The guide says an IAM condition lacking these does not match the namespace on which the service acts.",
              "source_ids": [
                "aws-memory-namespaces"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Can an AgentCore namespace IAM condition omit its leading or trailing slash? Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string. Normalised namespace string controls whether IAM conditions match. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "aws-memory-namespaces"
              ]
            },
            "buyer_evidence_required": [
              "normalised namespace",
              "request value",
              "IAM condition",
              "strategy template",
              "denied/allowed test evidence"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string."
            },
            "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": "aws-memory-namespaces",
                "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
                "final_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
                "captured_at_utc": "2026-10-30T18:22:06.260178+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 29216,
                "sha256": "688a03466c4ca5c15ab9de6eb1ac731d466adfb0f51e48abfff705f60536af85",
                "title": "Amazon Web Services primary documentation: aws memory namespaces",
                "publisher": "Amazon Web Services",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Namespace format",
                  "NamespaceResolutionFailure",
                  "Update namespace keys"
                ]
              }
            ],
            "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": "Can an AgentCore namespace IAM condition omit its leading or trailing slash? Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.",
              "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": "Namespace format"
            },
            "buyer_relevance": "Can an AgentCore namespace IAM condition omit its leading or trailing slash? Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.",
            "refusal_conditions": [
              "Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Can an AgentCore namespace IAM condition omit its leading or trailing slash?",
              "consequence": "Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B01",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-PINECONE-TENANT-ROUTING-01-v1",
              "nearest_record_url": "/varexis-index/records/pinecone-namespace-routing-evidence.json",
              "nearest_record_sha256": "360552e288e44294fe9cc73d3e3eee4ccdbcc00fad5125b202bd4d4cbbf24040",
              "material_distinction": "Normalised namespace string controls whether IAM conditions match. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-AGENTCORE-NORMALIZED-NAMESPACE-IAM-01-v1"
              },
              "record_url": "/varexis-index/records/agentcore-normalized-namespace-iam.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Can an AgentCore namespace IAM condition omit its leading or trailing slash? Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.",
            "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#agentcore-normalized-namespace-iam",
          "machine_readable_record": "/varexis-index/records/agentcore-normalized-namespace-iam.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-AGENTCORE-CUSTOM-NAMESPACE-EXTRACTION-GAP-01-v1",
        "url": "/varexis-index/records/agentcore-custom-namespace-extraction-gap.json",
        "content_sha256": "1c39e7f868e5192004987b6afb610b8bc52d57ef81bb04d6968d19008573a784",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-AGENTCORE-CUSTOM-NAMESPACE-EXTRACTION-GAP-01-v1",
          "record_kind": "external_reference",
          "title": "Successful CreateEvent can persist short-term event while strategy extraction is skipped",
          "system": "Amazon Web Services",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran?",
          "near_questions": [
            "Can AgentCore CreateEvent succeed while memory extraction does not start?",
            "What happens when an AgentCore strategy lacks a namespace variable?",
            "Does short-term event storage prove long-term memory formation?",
            "What does AgentCore NamespaceResolutionFailure mean for extraction evidence?"
          ],
          "supported_claims": [
            {
              "claim": "AWS states that when CreateEvent omits a custom namespace variable referenced by a strategy template, extraction is not initiated for that strategy even though the event succeeds and persists in short-term memory. NamespaceResolutionFailure metrics identify the skipped strategy.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.",
            "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": "AWS states that when CreateEvent omits a custom namespace variable referenced by a strategy template, extraction is not initiated for that strategy even though the event succeeds and persists in short-term memory. NamespaceResolutionFailure metrics identify the skipped strategy.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Amazon Web Services primary documentation: aws memory namespaces",
            "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-AGENTCORE-CUSTOM-NAMESPACE-EXTRACTION-GAP-01-v1",
            "candidate_record_sha256": "98be40efe10723826f7ba19c04ce1378faa73714d89f4ac5d4a7da284452632d",
            "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": "AWS states that when CreateEvent omits a custom namespace variable referenced by a strategy template, extraction is not initiated for that strategy even though the event succeeds and persists in short-term memory. NamespaceResolutionFailure metrics identify the skipped strategy.",
            "required_buyer_context": "namespace-key schema; runtime values; strategy templates; extraction/skip metrics; event ID. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran?",
            "documented_statement": {
              "status": "documented",
              "statement": "AWS states that when CreateEvent omits a custom namespace variable referenced by a strategy template, extraction is not initiated for that strategy even though the event succeeds and persists in short-term memory. NamespaceResolutionFailure metrics identify the skipped strategy.",
              "source_ids": [
                "aws-memory-namespaces"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran? Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction. Successful CreateEvent can persist short-term event while strategy extraction is skipped. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "aws-memory-namespaces"
              ]
            },
            "buyer_evidence_required": [
              "namespace-key schema",
              "runtime values",
              "strategy templates",
              "extraction/skip metrics",
              "event ID"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction."
            },
            "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": "aws-memory-namespaces",
                "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
                "final_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
                "captured_at_utc": "2026-10-30T18:22:06.260178+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 29216,
                "sha256": "688a03466c4ca5c15ab9de6eb1ac731d466adfb0f51e48abfff705f60536af85",
                "title": "Amazon Web Services primary documentation: aws memory namespaces",
                "publisher": "Amazon Web Services",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Namespace format",
                  "NamespaceResolutionFailure",
                  "Update namespace keys"
                ]
              }
            ],
            "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": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran? Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.",
              "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": "NamespaceResolutionFailure"
            },
            "buyer_relevance": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran? Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.",
            "refusal_conditions": [
              "Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran?",
              "consequence": "Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B02",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-AWS-AC-ID-01-v1",
              "nearest_record_url": "/varexis-index/records/aws-agentcore-workload-identity.json",
              "nearest_record_sha256": "4b471e827fb8c1961069f4f78f683a120d353bd7e30947e0dfff332613d92ef6",
              "material_distinction": "Successful CreateEvent can persist short-term event while strategy extraction is skipped. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-AGENTCORE-CUSTOM-NAMESPACE-EXTRACTION-GAP-01-v1"
              },
              "record_url": "/varexis-index/records/agentcore-custom-namespace-extraction-gap.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does accepting an AgentCore event prove all intended tenant-scoped extraction ran? Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.",
            "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#agentcore-custom-namespace-extraction-gap",
          "machine_readable_record": "/varexis-index/records/agentcore-custom-namespace-extraction-gap.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-AGENTCORE-NAMESPACE-KEY-REPLACEMENT-01-v1",
        "url": "/varexis-index/records/agentcore-namespace-key-replacement.json",
        "content_sha256": "34a1c3e766b18217c82f770e8a7da77c2277ff6c3b5899ad9f209016585a0728",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-AGENTCORE-NAMESPACE-KEY-REPLACEMENT-01-v1",
          "record_kind": "external_reference",
          "title": "namespaceKeys update replaces full set and preserves dependent keys",
          "system": "Amazon Web Services",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does UpdateMemory append namespace keys while retaining the previous set?",
          "near_questions": [
            "Does an AgentCore namespaceKeys update merge or replace existing keys?",
            "What should be reconciled before changing memory namespace keys?",
            "Can omitting an old namespace key preserve it automatically?",
            "Which key set should an AgentCore memory update record retain?"
          ],
          "supported_claims": [
            {
              "claim": "The documented namespaceKeys update replaces the entire set. The guide requires preserving existing keys and rejects removing a key still used by a strategy template.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.",
            "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": "The documented namespaceKeys update replaces the entire set. The guide requires preserving existing keys and rejects removing a key still used by a strategy template.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Amazon Web Services primary documentation: aws memory namespaces",
            "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-AGENTCORE-NAMESPACE-KEY-REPLACEMENT-01-v1",
            "candidate_record_sha256": "9029bbe0e49cd1eddb052bc98c238287d68cb39d6878c560d905cb939b5da80c",
            "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": "The documented namespaceKeys update replaces the entire set. The guide requires preserving existing keys and rejects removing a key still used by a strategy template.",
            "required_buyer_context": "before/after key sets; dependent namespace templates; update request/response; approval. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does UpdateMemory append namespace keys while retaining the previous set?",
            "documented_statement": {
              "status": "documented",
              "statement": "The documented namespaceKeys update replaces the entire set. The guide requires preserving existing keys and rejects removing a key still used by a strategy template.",
              "source_ids": [
                "aws-memory-namespaces"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does UpdateMemory append namespace keys while retaining the previous set? Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving. namespaceKeys update replaces full set and preserves dependent keys. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "aws-memory-namespaces"
              ]
            },
            "buyer_evidence_required": [
              "before/after key sets",
              "dependent namespace templates",
              "update request/response",
              "approval"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving."
            },
            "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": "aws-memory-namespaces",
                "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
                "final_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.html",
                "captured_at_utc": "2026-10-30T18:22:06.260178+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 29216,
                "sha256": "688a03466c4ca5c15ab9de6eb1ac731d466adfb0f51e48abfff705f60536af85",
                "title": "Amazon Web Services primary documentation: aws memory namespaces",
                "publisher": "Amazon Web Services",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Namespace format",
                  "NamespaceResolutionFailure",
                  "Update namespace keys"
                ]
              }
            ],
            "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": "Does UpdateMemory append namespace keys while retaining the previous set? Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.",
              "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": "Update namespace keys"
            },
            "buyer_relevance": "Does UpdateMemory append namespace keys while retaining the previous set? Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.",
            "refusal_conditions": [
              "Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does UpdateMemory append namespace keys while retaining the previous set?",
              "consequence": "Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B03",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-GITHUB-DEPLOY-KEY-OFFBOARDING-RESIDUAL-ACCESS-01-v1",
              "nearest_record_url": "/varexis-index/records/github-deploy-key-offboarding-residual-access.json",
              "nearest_record_sha256": "4827b92c0b8970ddd179ad7f4342fc5adaeea302719b016b66d24a2cee998741",
              "material_distinction": "namespaceKeys update replaces full set and preserves dependent keys. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-AGENTCORE-NAMESPACE-KEY-REPLACEMENT-01-v1"
              },
              "record_url": "/varexis-index/records/agentcore-namespace-key-replacement.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does UpdateMemory append namespace keys while retaining the previous set? Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.",
            "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#agentcore-namespace-key-replacement",
          "machine_readable_record": "/varexis-index/records/agentcore-namespace-key-replacement.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-AGENTCORE-LONGTERM-RETENTION-PRUNER-01-v1",
        "url": "/varexis-index/records/agentcore-longterm-retention-pruner.json",
        "content_sha256": "51a3c87ad9c95c1d440dcfbd1af216ad17c27e05ba2ca23c6528e4d64a4b4d25",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-AGENTCORE-LONGTERM-RETENTION-PRUNER-01-v1",
          "record_kind": "external_reference",
          "title": "Long-term expiry requires deployed/executed timestamp-based pruner in reviewed design, distinct from DeleteEvent-derived residue",
          "system": "Amazon Web Services",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does a configured memory age prove AgentCore long-term records expire automatically?",
          "near_questions": [
            "Does a long-term AgentCore memory TTL policy execute deletion by itself?",
            "What evidence shows the AgentCore memory pruner actually ran?",
            "Can short-term event expiry establish long-term memory retention compliance?",
            "What separates a memory age rule from its pruning workflow?"
          ],
          "supported_claims": [
            {
              "claim": "The reviewed AWS lifecycle design implements timestamp-filtered pruning in a separate workflow and states that AgentCore memory lacks a built-in auto-delete TTL in that design context.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.",
            "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": "The reviewed AWS lifecycle design implements timestamp-filtered pruning in a separate workflow and states that AgentCore memory lacks a built-in auto-delete TTL in that design context.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Amazon Web Services primary documentation: aws memory lifecycle",
            "source_url": "https://aws.amazon.com/blogs/machine-learning/designing-lifecycle-policies-for-agentcore-memory/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-AGENTCORE-LONGTERM-RETENTION-PRUNER-01-v1",
            "candidate_record_sha256": "46dc28c4d6d88f967ba502870e13e98e7425ca0856588ae92a5f51005399d630",
            "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": "The reviewed AWS lifecycle design implements timestamp-filtered pruning in a separate workflow and states that AgentCore memory lacks a built-in auto-delete TTL in that design context.",
            "required_buyer_context": "memory class; configured policy; scheduler/workflow; record timestamps; deletion/reconciliation 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does a configured memory age prove AgentCore long-term records expire automatically?",
            "documented_statement": {
              "status": "documented",
              "statement": "The reviewed AWS lifecycle design implements timestamp-filtered pruning in a separate workflow and states that AgentCore memory lacks a built-in auto-delete TTL in that design context.",
              "source_ids": [
                "aws-memory-lifecycle"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does a configured memory age prove AgentCore long-term records expire automatically? A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence. Long-term expiry requires deployed/executed timestamp-based pruner in reviewed design, distinct from DeleteEvent-derived residue. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "aws-memory-lifecycle"
              ]
            },
            "buyer_evidence_required": [
              "memory class",
              "configured policy",
              "scheduler/workflow",
              "record timestamps",
              "deletion/reconciliation results"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence."
            },
            "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": "aws-memory-lifecycle",
                "url": "https://aws.amazon.com/blogs/machine-learning/designing-lifecycle-policies-for-agentcore-memory/",
                "final_url": "https://aws.amazon.com/blogs/machine-learning/designing-lifecycle-policies-for-agentcore-memory/",
                "captured_at_utc": "2026-10-30T18:22:06.360586+00:00",
                "status": 200,
                "content_type": "text/html;charset=UTF-8",
                "bytes": 1465702,
                "sha256": "317cb423a95b0f0ecf16ac2d86e70fbe7abfabff8afe092ac9f9e4cf1224cc86",
                "title": "Amazon Web Services primary documentation: aws memory lifecycle",
                "publisher": "Amazon Web Services",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "doesn’t provide a built-in auto-delete TTL"
                ]
              }
            ],
            "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": "Does a configured memory age prove AgentCore long-term records expire automatically? A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.",
              "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": "doesn’t provide a built-in auto-delete TTL"
            },
            "buyer_relevance": "Does a configured memory age prove AgentCore long-term records expire automatically? A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.",
            "refusal_conditions": [
              "A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does a configured memory age prove AgentCore long-term records expire automatically?",
              "consequence": "A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B04",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-EVENT-DELETE-DERIVED-MEMORY-RESIDUE-01-v1",
              "nearest_record_url": "/varexis-index/records/agentcore-event-delete-derived-memory-residue.json",
              "nearest_record_sha256": "240ae602db6e63a80b00e3ac83e9f384479e7a89b7dc19679e92a20ea1f579b4",
              "material_distinction": "Long-term expiry requires deployed/executed timestamp-based pruner in reviewed design, distinct from DeleteEvent-derived residue. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-AGENTCORE-LONGTERM-RETENTION-PRUNER-01-v1"
              },
              "record_url": "/varexis-index/records/agentcore-longterm-retention-pruner.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does a configured memory age prove AgentCore long-term records expire automatically? A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.",
            "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#agentcore-longterm-retention-pruner",
          "machine_readable_record": "/varexis-index/records/agentcore-longterm-retention-pruner.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-VERBATIM-TRANSCRIPT-CUSTODY-01-v1",
        "url": "/varexis-index/records/cloudflare-memory-verbatim-transcript-custody.json",
        "content_sha256": "f495f13f018eb89e8041d13e4864f05d1ee5e89c0e079331cac888584c656c25",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-VERBATIM-TRANSCRIPT-CUSTODY-01-v1",
          "record_kind": "external_reference",
          "title": "Private-beta ingestion retains raw transcript as well as extracted facts",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation?",
          "near_questions": [
            "Does Cloudflare Agent Memory retain raw transcripts as well as extracted facts?",
            "Can a facts-only inventory omit Cloudflare conversation messages?",
            "Which source text is searched by the documented private-beta memory service?",
            "What raw-message custody evidence is required beyond extracted memories?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The reviewed beta documentation says raw messages are stored verbatim alongside extracted memories and are also searched during recall.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The reviewed beta documentation says raw messages are stored verbatim alongside extracted memories and are also searched during recall.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory how",
            "source_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-VERBATIM-TRANSCRIPT-CUSTODY-01-v1",
            "candidate_record_sha256": "a4a8fc3c8bf841f55baede0c9174ba3870168f9c3fd59cf3fd201397746d94f9",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The reviewed beta documentation says raw messages are stored verbatim alongside extracted memories and are also searched during recall.",
            "required_buyer_context": "namespace/profile/session IDs; ingestion payload scope; transcript and extracted-memory inventory; retention policy. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The reviewed beta documentation says raw messages are stored verbatim alongside extracted memories and are also searched during recall.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation? Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation. Private-beta ingestion retains raw transcript as well as extracted facts. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "buyer_evidence_required": [
              "namespace/profile/session IDs",
              "ingestion payload scope",
              "transcript and extracted-memory inventory",
              "retention policy"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-how",
                "url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "final_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "captured_at_utc": "2026-10-30T18:28:58.475816+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 106575,
                "sha256": "5d39e5cfb3a4f65c0b792c2d312999460d00c3f017454ba4d99688fa895b9384",
                "title": "Cloudflare primary documentation: cloudflare memory how",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Raw conversation messages are always stored verbatim",
                  "full history is preserved",
                  "Tasks are deprioritized",
                  "Messages are content-addressed"
                ]
              }
            ],
            "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": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation? Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.",
              "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": "Raw conversation messages are always stored verbatim"
            },
            "buyer_relevance": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation? Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation?",
              "consequence": "Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B06",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
              "nearest_record_url": "/varexis-index/records/copilot-conversation-deletion-memory-separation.json",
              "nearest_record_sha256": "d50b322fa3e23edbe51363ab32c6eb085bb8c4c200098ad2bde3d095ec511e82",
              "material_distinction": "Private-beta ingestion retains raw transcript as well as extracted facts. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-VERBATIM-TRANSCRIPT-CUSTODY-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-memory-verbatim-transcript-custody.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation? Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-memory-verbatim-transcript-custody",
          "machine_readable_record": "/varexis-index/records/cloudflare-memory-verbatim-transcript-custody.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-SUPERSEDED-MEMORY-RESIDUE-01-v1",
        "url": "/varexis-index/records/cloudflare-superseded-memory-residue.json",
        "content_sha256": "9f851daa6008348669de3d06a13a243da57798f2ce9aca0b6b090f6fe1c4b023",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-SUPERSEDED-MEMORY-RESIDUE-01-v1",
          "record_kind": "external_reference",
          "title": "Supersession preserves old history despite latest-first recall",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does a newer Cloudflare memory fact replace and erase the previous fact?",
          "near_questions": [
            "Does superseding a Cloudflare memory remove its earlier history?",
            "Can corrected private-beta memory facts leave previous values stored?",
            "What residue should a Cloudflare memory correction review consider?",
            "Does a current memory value establish disposal of its predecessor?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta documentation describes facts and instructions being superseded by topic key while retaining old versions; recall preferentially surfaces the latest version.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta documentation describes facts and instructions being superseded by topic key while retaining old versions; recall preferentially surfaces the latest version.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory how",
            "source_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-SUPERSEDED-MEMORY-RESIDUE-01-v1",
            "candidate_record_sha256": "896d76dd772eb39b53f8e1ea9cc49032ec11955e655b3118dbcdd65e16783247",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta documentation describes facts and instructions being superseded by topic key while retaining old versions; recall preferentially surfaces the latest version.",
            "required_buyer_context": "topic key; old/new memory IDs; supersession state; history inventory; deletion scope. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does a newer Cloudflare memory fact replace and erase the previous fact?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta documentation describes facts and instructions being superseded by topic key while retaining old versions; recall preferentially surfaces the latest version.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does a newer Cloudflare memory fact replace and erase the previous fact? Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation. Supersession preserves old history despite latest-first recall. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "buyer_evidence_required": [
              "topic key",
              "old/new memory IDs",
              "supersession state",
              "history inventory",
              "deletion scope"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-how",
                "url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "final_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "captured_at_utc": "2026-10-30T18:28:58.475816+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 106575,
                "sha256": "5d39e5cfb3a4f65c0b792c2d312999460d00c3f017454ba4d99688fa895b9384",
                "title": "Cloudflare primary documentation: cloudflare memory how",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Raw conversation messages are always stored verbatim",
                  "full history is preserved",
                  "Tasks are deprioritized",
                  "Messages are content-addressed"
                ]
              }
            ],
            "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": "Does a newer Cloudflare memory fact replace and erase the previous fact? Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.",
              "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": "full history is preserved"
            },
            "buyer_relevance": "Does a newer Cloudflare memory fact replace and erase the previous fact? Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does a newer Cloudflare memory fact replace and erase the previous fact?",
              "consequence": "Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B07",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-GCP-KMS-ROTATION-DATA-01-v1",
              "nearest_record_url": "/varexis-index/records/gcp-kms-rotation-existing-data.json",
              "nearest_record_sha256": "f33ed61511537904980967243383f3268457b4bfe480bd5a7d06ad1617cb8b15",
              "material_distinction": "Supersession preserves old history despite latest-first recall. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-SUPERSEDED-MEMORY-RESIDUE-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-superseded-memory-residue.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does a newer Cloudflare memory fact replace and erase the previous fact? Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-superseded-memory-residue",
          "machine_readable_record": "/varexis-index/records/cloudflare-superseded-memory-residue.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-PROFILE-SESSION-BOUNDARIES-01-v1",
        "url": "/varexis-index/records/cloudflare-profile-session-boundaries.json",
        "content_sha256": "5d538ff820d56b8a8147fe344cf47bdc7c97e50ee51923e710c95efd3f25bb4c",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-PROFILE-SESSION-BOUNDARIES-01-v1",
          "record_kind": "external_reference",
          "title": "Namespace/profile/session tuple versus authenticated tenant boundary",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary?",
          "near_questions": [
            "Are Cloudflare Agent Memory session identifiers global across profiles?",
            "Which namespace and profile boundaries apply to memory sessions?",
            "Can a session ID alone identify a Cloudflare memory owner?",
            "What identity mapping must accompany a private-beta memory profile?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented hierarchy separates namespaces and profiles, with sessions scoped to a profile and the same session ID permitted in different profiles. Recall is described as confined to the selected profile.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented hierarchy separates namespaces and profiles, with sessions scoped to a profile and the same session ID permitted in different profiles. Recall is described as confined to the selected profile.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory profiles",
            "source_url": "https://developers.cloudflare.com/agent-memory/concepts/namespaces-profiles/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-PROFILE-SESSION-BOUNDARIES-01-v1",
            "candidate_record_sha256": "a1bc6cc695d887832343637d83d44db439dad9b502e4b1511e12a0779292c47f",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented hierarchy separates namespaces and profiles, with sessions scoped to a profile and the same session ID permitted in different profiles. Recall is described as confined to the selected profile.",
            "required_buyer_context": "account/namespace/profile tuple; session ID; identity mapping; API token permissions; isolation tests. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented hierarchy separates namespaces and profiles, with sessions scoped to a profile and the same session ID permitted in different profiles. Recall is described as confined to the selected profile.",
              "source_ids": [
                "cloudflare-memory-profiles"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary? Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation. Namespace/profile/session tuple versus authenticated tenant boundary. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-profiles"
              ]
            },
            "buyer_evidence_required": [
              "account/namespace/profile tuple",
              "session ID",
              "identity mapping",
              "API token permissions",
              "isolation tests"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-profiles",
                "url": "https://developers.cloudflare.com/agent-memory/concepts/namespaces-profiles/",
                "final_url": "https://developers.cloudflare.com/agent-memory/concepts/namespaces-profiles/",
                "captured_at_utc": "2026-10-30T18:28:58.469096+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 95628,
                "sha256": "0f8fb31dad82e3f373fffbb8981a609703c21d9223a7f2923c058e638b557e82",
                "title": "Cloudflare primary documentation: cloudflare memory profiles",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Sessions are scoped to a profile"
                ]
              }
            ],
            "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": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary? Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.",
              "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": "Sessions are scoped to a profile"
            },
            "buyer_relevance": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary? Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary?",
              "consequence": "Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B08",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-SAAS-SESSION-01-v1",
              "nearest_record_url": "/varexis-index/records/cloudflare-access-saas-session-boundary.json",
              "nearest_record_sha256": "5fcb6993129d6a97c362c1190d07fffe81322a4f612568d2e27afdc96fa7f2b6",
              "material_distinction": "Namespace/profile/session tuple versus authenticated tenant boundary. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-PROFILE-SESSION-BOUNDARIES-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-profile-session-boundaries.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Can a Cloudflare Agent Memory session identifier alone define a tenant boundary? Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-profile-session-boundaries",
          "machine_readable_record": "/varexis-index/records/cloudflare-profile-session-boundaries.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-TASK-DEPRIORITIZATION-RETENTION-01-v1",
        "url": "/varexis-index/records/cloudflare-task-deprioritization-retention.json",
        "content_sha256": "0f50801886d3c5b63d684d78da1a262022a04f65640371ba527259514922b16e",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-TASK-DEPRIORITIZATION-RETENTION-01-v1",
          "record_kind": "external_reference",
          "title": "Task deprioritisation after session end versus deletion",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does ending a Cloudflare Agent Memory session delete its task memories?",
          "near_questions": [
            "Does deprioritising a Cloudflare memory task delete it?",
            "Can a completed task be omitted from a retained-data inventory?",
            "What is the retention implication of task prioritisation in Agent Memory?",
            "Does lower retrieval priority establish erasure of a task memory?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented task class is session-scoped and deprioritised after the session ends. Deprioritisation describes retrieval treatment rather than an asserted deletion operation.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented task class is session-scoped and deprioritised after the session ends. Deprioritisation describes retrieval treatment rather than an asserted deletion operation.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory how",
            "source_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-TASK-DEPRIORITIZATION-RETENTION-01-v1",
            "candidate_record_sha256": "573903438327b81d04191a60181a89f9b51b5b7e5937ef0459d3d6a81099fb1a",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented task class is session-scoped and deprioritised after the session ends. Deprioritisation describes retrieval treatment rather than an asserted deletion operation.",
            "required_buyer_context": "task memory IDs; session lifecycle; recall behaviour; applicable deletion/retention evidence. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does ending a Cloudflare Agent Memory session delete its task memories?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented task class is session-scoped and deprioritised after the session ends. Deprioritisation describes retrieval treatment rather than an asserted deletion operation.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does ending a Cloudflare Agent Memory session delete its task memories? Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation. Task deprioritisation after session end versus deletion. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "buyer_evidence_required": [
              "task memory IDs",
              "session lifecycle",
              "recall behaviour",
              "applicable deletion/retention evidence"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-how",
                "url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "final_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "captured_at_utc": "2026-10-30T18:28:58.475816+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 106575,
                "sha256": "5d39e5cfb3a4f65c0b792c2d312999460d00c3f017454ba4d99688fa895b9384",
                "title": "Cloudflare primary documentation: cloudflare memory how",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Raw conversation messages are always stored verbatim",
                  "full history is preserved",
                  "Tasks are deprioritized",
                  "Messages are content-addressed"
                ]
              }
            ],
            "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": "Does ending a Cloudflare Agent Memory session delete its task memories? Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.",
              "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": "Tasks are deprioritized"
            },
            "buyer_relevance": "Does ending a Cloudflare Agent Memory session delete its task memories? Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does ending a Cloudflare Agent Memory session delete its task memories?",
              "consequence": "Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B09",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
              "nearest_record_url": "/varexis-index/records/copilot-conversation-deletion-memory-separation.json",
              "nearest_record_sha256": "d50b322fa3e23edbe51363ab32c6eb085bb8c4c200098ad2bde3d095ec511e82",
              "material_distinction": "Task deprioritisation after session end versus deletion. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-TASK-DEPRIORITIZATION-RETENTION-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-task-deprioritization-retention.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does ending a Cloudflare Agent Memory session delete its task memories? Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-task-deprioritization-retention",
          "machine_readable_record": "/varexis-index/records/cloudflare-task-deprioritization-retention.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-DELETE-SCOPE-01-v1",
        "url": "/varexis-index/records/cloudflare-memory-delete-scope.json",
        "content_sha256": "123e0cf725e2ebd0859415b452780734a337513f75454f8049660e6c6eff90a8",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-DELETE-SCOPE-01-v1",
          "record_kind": "external_reference",
          "title": "Individual memory/source-message deletion versus whole-profile scope",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does deleting one Cloudflare memory establish deletion of its whole profile?",
          "near_questions": [
            "Which Cloudflare Agent Memory delete operation matches the requested scope?",
            "Does deleting one memory remove every profile or session?",
            "How do linked messages affect a memory deletion review?",
            "What deletion target should a private-beta memory receipt identify?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API distinguishes namespace, profile, session and individual-memory deletion. Its individual-memory description removes that memory and source messages linked to it, rather than asserting complete profile erasure.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API distinguishes namespace, profile, session and individual-memory deletion. Its individual-memory description removes that memory and source messages linked to it, rather than asserting complete profile erasure.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory api",
            "source_url": "https://developers.cloudflare.com/agent-memory/api/http-api/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-DELETE-SCOPE-01-v1",
            "candidate_record_sha256": "7d8abcb8165ee4d2b6ef2913459046547f4e7b2791baca52687cef71d2f655a7",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API distinguishes namespace, profile, session and individual-memory deletion. Its individual-memory description removes that memory and source messages linked to it, rather than asserting complete profile erasure.",
            "required_buyer_context": "exact deletion endpoint; namespace/profile/session/memory IDs; response; residual representations. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does deleting one Cloudflare memory establish deletion of its whole profile?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API distinguishes namespace, profile, session and individual-memory deletion. Its individual-memory description removes that memory and source messages linked to it, rather than asserting complete profile erasure.",
              "source_ids": [
                "cloudflare-memory-api"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does deleting one Cloudflare memory establish deletion of its whole profile? Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation. Individual memory/source-message deletion versus whole-profile scope. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-api"
              ]
            },
            "buyer_evidence_required": [
              "exact deletion endpoint",
              "namespace/profile/session/memory IDs",
              "response",
              "residual representations"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-api",
                "url": "https://developers.cloudflare.com/agent-memory/api/http-api/",
                "final_url": "https://developers.cloudflare.com/agent-memory/api/http-api/",
                "captured_at_utc": "2026-10-30T18:28:07.223333+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 151959,
                "sha256": "fb91236a387f06b817cbc1ba463b74b43299f7ea792572026de812772d4386a3",
                "title": "Cloudflare primary documentation: cloudflare memory api",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Delete a memory",
                  "Remember a memory"
                ]
              }
            ],
            "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": "Does deleting one Cloudflare memory establish deletion of its whole profile? Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.",
              "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": "Delete a memory"
            },
            "buyer_relevance": "Does deleting one Cloudflare memory establish deletion of its whole profile? Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does deleting one Cloudflare memory establish deletion of its whole profile?",
              "consequence": "Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B10",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-EVENT-DELETE-DERIVED-MEMORY-RESIDUE-01-v1",
              "nearest_record_url": "/varexis-index/records/agentcore-event-delete-derived-memory-residue.json",
              "nearest_record_sha256": "240ae602db6e63a80b00e3ac83e9f384479e7a89b7dc19679e92a20ea1f579b4",
              "material_distinction": "Individual memory/source-message deletion versus whole-profile scope. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-MEMORY-DELETE-SCOPE-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-memory-delete-scope.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does deleting one Cloudflare memory establish deletion of its whole profile? Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-memory-delete-scope",
          "machine_readable_record": "/varexis-index/records/cloudflare-memory-delete-scope.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-CONTENT-SESSION-DEDUPLICATION-01-v1",
        "url": "/varexis-index/records/cloudflare-content-session-deduplication.json",
        "content_sha256": "2c236166b227465bf8063257cccd15a68ef9d97f7f81975cb6876c29cff3b6af",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-CONTENT-SESSION-DEDUPLICATION-01-v1",
          "record_kind": "external_reference",
          "title": "Content-and-session identity bounds ingestion deduplication",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does retrying Cloudflare memory ingestion always preserve the same message identity?",
          "near_questions": [
            "How does Cloudflare Agent Memory derive message and session identifiers?",
            "Can identical text in different sessions have different message identities?",
            "What context is needed to assess Cloudflare memory deduplication?",
            "Can content-based session identity change after the input changes?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta design derives message IDs from content and session and can derive an omitted session ID from the conversation. Its deduplication therefore depends on those inputs.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta design derives message IDs from content and session and can derive an omitted session ID from the conversation. Its deduplication therefore depends on those inputs.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory how",
            "source_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-CONTENT-SESSION-DEDUPLICATION-01-v1",
            "candidate_record_sha256": "4eed1f45d257a52748f4f9602184d6ed84002efca8b3a00c57743de795d3773a",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta design derives message IDs from content and session and can derive an omitted session ID from the conversation. Its deduplication therefore depends on those inputs.",
            "required_buyer_context": "message content hash; session mapping; retry inputs; ingestion responses; resulting inventory. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does retrying Cloudflare memory ingestion always preserve the same message identity?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta design derives message IDs from content and session and can derive an omitted session ID from the conversation. Its deduplication therefore depends on those inputs.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does retrying Cloudflare memory ingestion always preserve the same message identity? Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation. Content-and-session identity bounds ingestion deduplication. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-how"
              ]
            },
            "buyer_evidence_required": [
              "message content hash",
              "session mapping",
              "retry inputs",
              "ingestion responses",
              "resulting inventory"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-how",
                "url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "final_url": "https://developers.cloudflare.com/agent-memory/concepts/how-agent-memory-works/",
                "captured_at_utc": "2026-10-30T18:28:58.475816+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 106575,
                "sha256": "5d39e5cfb3a4f65c0b792c2d312999460d00c3f017454ba4d99688fa895b9384",
                "title": "Cloudflare primary documentation: cloudflare memory how",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Raw conversation messages are always stored verbatim",
                  "full history is preserved",
                  "Tasks are deprioritized",
                  "Messages are content-addressed"
                ]
              }
            ],
            "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": "Does retrying Cloudflare memory ingestion always preserve the same message identity? Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.",
              "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": "Messages are content-addressed"
            },
            "buyer_relevance": "Does retrying Cloudflare memory ingestion always preserve the same message identity? Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does retrying Cloudflare memory ingestion always preserve the same message identity?",
              "consequence": "Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B11",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
              "nearest_record_url": "/varexis-index/records/copilot-conversation-deletion-memory-separation.json",
              "nearest_record_sha256": "d50b322fa3e23edbe51363ab32c6eb085bb8c4c200098ad2bde3d095ec511e82",
              "material_distinction": "Content-and-session identity bounds ingestion deduplication. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-CONTENT-SESSION-DEDUPLICATION-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-content-session-deduplication.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does retrying Cloudflare memory ingestion always preserve the same message identity? Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-content-session-deduplication",
          "machine_readable_record": "/varexis-index/records/cloudflare-content-session-deduplication.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-CLOUDFLARE-DIRECT-REMEMBER-EXTRACTION-CHOICE-01-v1",
        "url": "/varexis-index/records/cloudflare-direct-remember-extraction-choice.json",
        "content_sha256": "3d616df2f4b850469090dee4f4403b7f6cde0a881ddb13b091c252d04b8d5151",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-CLOUDFLARE-DIRECT-REMEMBER-EXTRACTION-CHOICE-01-v1",
          "record_kind": "external_reference",
          "title": "Application-supplied direct memory versus extracted conversation provenance and authority",
          "system": "Cloudflare",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion?",
          "near_questions": [
            "How does Cloudflare remember differ from message ingestion?",
            "Can direct memory insertion be treated as an extracted fact?",
            "What provenance distinguishes supplied memories from extraction outputs?",
            "Which write path should a Cloudflare memory inventory preserve?"
          ],
          "supported_claims": [
            {
              "claim": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API provides separate conversation-ingestion and direct-memory operations, allowing an application to supply a memory rather than relying only on extracted conversation content.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API provides separate conversation-ingestion and direct-memory operations, allowing an application to supply a memory rather than relying only on extracted conversation content.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Cloudflare primary documentation: cloudflare memory api",
            "source_url": "https://developers.cloudflare.com/agent-memory/api/http-api/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-CLOUDFLARE-DIRECT-REMEMBER-EXTRACTION-CHOICE-01-v1",
            "candidate_record_sha256": "8723d24aac62625ad9a8eb71d4d7ecc98016d3139bab7c7afa93eb84218ff9e7",
            "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": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API provides separate conversation-ingestion and direct-memory operations, allowing an application to supply a memory rather than relying only on extracted conversation content.",
            "required_buyer_context": "operation type; supplied memory or conversation; consent/use basis; namespace/profile; resulting IDs. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. PRIVATE BETA at review date; no general-availability or stable-contract assertion.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion?",
            "documented_statement": {
              "status": "documented",
              "statement": "Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API provides separate conversation-ingestion and direct-memory operations, allowing an application to supply a memory rather than relying only on extracted conversation content.",
              "source_ids": [
                "cloudflare-memory-api"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion? Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation. Application-supplied direct memory versus extracted conversation provenance and authority. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "cloudflare-memory-api"
              ]
            },
            "buyer_evidence_required": [
              "operation type",
              "supplied memory or conversation",
              "consent/use basis",
              "namespace/profile",
              "resulting IDs"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation."
            },
            "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": "cloudflare-memory-api",
                "url": "https://developers.cloudflare.com/agent-memory/api/http-api/",
                "final_url": "https://developers.cloudflare.com/agent-memory/api/http-api/",
                "captured_at_utc": "2026-10-30T18:28:07.223333+00:00",
                "status": 200,
                "content_type": "text/html",
                "bytes": 151959,
                "sha256": "fb91236a387f06b817cbc1ba463b74b43299f7ea792572026de812772d4386a3",
                "title": "Cloudflare primary documentation: cloudflare memory api",
                "publisher": "Cloudflare",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. PRIVATE BETA at capture; no stable availability guarantee.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Delete a memory",
                  "Remember a memory"
                ]
              }
            ],
            "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": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion? Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.",
              "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": "Remember a memory"
            },
            "buyer_relevance": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion? Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.",
            "refusal_conditions": [
              "Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion?",
              "consequence": "Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B12",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
              "nearest_record_url": "/varexis-index/records/copilot-conversation-deletion-memory-separation.json",
              "nearest_record_sha256": "d50b322fa3e23edbe51363ab32c6eb085bb8c4c200098ad2bde3d095ec511e82",
              "material_distinction": "Application-supplied direct memory versus extracted conversation provenance and authority. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-CLOUDFLARE-DIRECT-REMEMBER-EXTRACTION-CHOICE-01-v1"
              },
              "record_url": "/varexis-index/records/cloudflare-direct-remember-extraction-choice.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion? Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.",
            "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#cloudflare-direct-remember-extraction-choice",
          "machine_readable_record": "/varexis-index/records/cloudflare-direct-remember-extraction-choice.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-MEM0-ADDITIVE-EXTRACTION-CORRECTION-01-v1",
        "url": "/varexis-index/records/mem0-additive-extraction-correction.json",
        "content_sha256": "e75844acc001f19f6c37b475c493a80e05ff956f2ecf8b92697b34406e96f7bf",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-MEM0-ADDITIVE-EXTRACTION-CORRECTION-01-v1",
          "record_kind": "external_reference",
          "title": "Additive extraction versus explicit correction/removal",
          "system": "Mem0",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does telling Mem0 a corrected fact automatically remove the earlier one?",
          "near_questions": [
            "Does adding a corrected Mem0 statement automatically replace an older memory?",
            "When does Mem0 correction require explicit update or deletion?",
            "Can additive extraction preserve conflicting old and new facts?",
            "What operation evidence supports a Mem0 memory correction claim?"
          ],
          "supported_claims": [
            {
              "claim": "The captured Mem0 documentation describes extraction as additive and recommends explicit update or delete for correction/removal; new information can be stored without rewriting an old fact.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.",
            "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": "The captured Mem0 documentation describes extraction as additive and recommends explicit update or delete for correction/removal; new information can be stored without rewriting an old fact.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Mem0 primary documentation: mem0 filters",
            "source_url": "https://docs.mem0.ai/core-concepts/memory-types.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-MEM0-ADDITIVE-EXTRACTION-CORRECTION-01-v1",
            "candidate_record_sha256": "54e3ad727e2cd7b14661bd74f798156f7ac8337df6593a6fbfde37d7f4fc9e60",
            "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": "The captured Mem0 documentation describes extraction as additive and recommends explicit update or delete for correction/removal; new information can be stored without rewriting an old fact.",
            "required_buyer_context": "old/new fact IDs; add/update/delete calls; entity filters; retrieval verification. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does telling Mem0 a corrected fact automatically remove the earlier one?",
            "documented_statement": {
              "status": "documented",
              "statement": "The captured Mem0 documentation describes extraction as additive and recommends explicit update or delete for correction/removal; new information can be stored without rewriting an old fact.",
              "source_ids": [
                "mem0-filters-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does telling Mem0 a corrected fact automatically remove the earlier one? Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations. Additive extraction versus explicit correction/removal. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "mem0-filters-md"
              ]
            },
            "buyer_evidence_required": [
              "old/new fact IDs",
              "add/update/delete calls",
              "entity filters",
              "retrieval verification"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations."
            },
            "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": "mem0-filters-md",
                "url": "https://docs.mem0.ai/core-concepts/memory-types.md",
                "final_url": "https://docs.mem0.ai/core-concepts/how-it-works.md",
                "captured_at_utc": "2026-10-30T18:29:16.577768+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 6263,
                "sha256": "43643261fc6e63a6d742e19be2ff50356152ccef33e05fc0071f3ac0ca8e59a8",
                "title": "Mem0 primary documentation: mem0 filters",
                "publisher": "Mem0",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "automatic extraction path is additive",
                  "Where memories live"
                ]
              }
            ],
            "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": "Does telling Mem0 a corrected fact automatically remove the earlier one? Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.",
              "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": "automatic extraction path is additive"
            },
            "buyer_relevance": "Does telling Mem0 a corrected fact automatically remove the earlier one? Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.",
            "refusal_conditions": [
              "Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does telling Mem0 a corrected fact automatically remove the earlier one?",
              "consequence": "Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B13",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-GITHUB-KEYS-01-v1",
              "nearest_record_url": "/varexis-index/records/github-app-private-key-rotation-lifecycle.json",
              "nearest_record_sha256": "a3e993b53a5cf906b495e0f11f214b471105f95dbe90b4fbe50185d940b7b164",
              "material_distinction": "Additive extraction versus explicit correction/removal. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-MEM0-ADDITIVE-EXTRACTION-CORRECTION-01-v1"
              },
              "record_url": "/varexis-index/records/mem0-additive-extraction-correction.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does telling Mem0 a corrected fact automatically remove the earlier one? Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.",
            "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#mem0-additive-extraction-correction",
          "machine_readable_record": "/varexis-index/records/mem0-additive-extraction-correction.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-MEM0-FILTERED-DELETE-WILDCARD-SCOPE-01-v1",
        "url": "/varexis-index/records/mem0-filtered-delete-wildcard-scope.json",
        "content_sha256": "80c4baea8c0b353dc7903c74a4cec9fc1558d6eb9f9a03825bf3a97e4b16d7fe",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-MEM0-FILTERED-DELETE-WILDCARD-SCOPE-01-v1",
          "record_kind": "external_reference",
          "title": "Documented managed delete wildcards require explicit full-project scope",
          "system": "Mem0",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Can a Mem0 user wildcard be treated as a complete project erasure?",
          "near_questions": [
            "What scope do Mem0 wildcard deletion filters select?",
            "Can an empty Mem0 delete filter mean delete everything?",
            "Which entity wildcards are required for the documented full-project deletion?",
            "How should a reviewer distinguish single batch and filtered Mem0 deletion?"
          ],
          "supported_claims": [
            {
              "claim": "The current documentation distinguishes scoped delete_all arguments, rejects missing/blank identifiers in SDKs, and requires all four entity filters set to wildcards for its described full-project wipe.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.",
            "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": "The current documentation distinguishes scoped delete_all arguments, rejects missing/blank identifiers in SDKs, and requires all four entity filters set to wildcards for its described full-project wipe.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Mem0 primary documentation: mem0 delete",
            "source_url": "https://docs.mem0.ai/core-concepts/memory-operations/delete.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-MEM0-FILTERED-DELETE-WILDCARD-SCOPE-01-v1",
            "candidate_record_sha256": "7281e2a9b13394e345005da904fe0b9c3ef09823df148e0b65da4cd055a81e46",
            "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": "The current documentation distinguishes scoped delete_all arguments, rejects missing/blank identifiers in SDKs, and requires all four entity filters set to wildcards for its described full-project wipe.",
            "required_buyer_context": "SDK/API version; user/agent/app/run filters; targeted ID inventory; deletion and recheck 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Can a Mem0 user wildcard be treated as a complete project erasure?",
            "documented_statement": {
              "status": "documented",
              "statement": "The current documentation distinguishes scoped delete_all arguments, rejects missing/blank identifiers in SDKs, and requires all four entity filters set to wildcards for its described full-project wipe.",
              "source_ids": [
                "mem0-delete-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Can a Mem0 user wildcard be treated as a complete project erasure? Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation. Documented managed delete wildcards require explicit full-project scope. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "mem0-delete-md"
              ]
            },
            "buyer_evidence_required": [
              "SDK/API version",
              "user/agent/app/run filters",
              "targeted ID inventory",
              "deletion and recheck results"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation."
            },
            "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": "mem0-delete-md",
                "url": "https://docs.mem0.ai/core-concepts/memory-operations/delete.md",
                "final_url": "https://docs.mem0.ai/core-concepts/memory-operations/delete.md",
                "captured_at_utc": "2026-10-30T18:29:16.799867+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 7617,
                "sha256": "8f1a9f465a5cb33756549227e18b92143ee955fcf91fbd169e5f4abf41d17db7",
                "title": "Mem0 primary documentation: mem0 delete",
                "publisher": "Mem0",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Wildcard deletes"
                ]
              }
            ],
            "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": "Can a Mem0 user wildcard be treated as a complete project erasure? Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.",
              "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": "Wildcard deletes"
            },
            "buyer_relevance": "Can a Mem0 user wildcard be treated as a complete project erasure? Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.",
            "refusal_conditions": [
              "Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Can a Mem0 user wildcard be treated as a complete project erasure?",
              "consequence": "Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B14",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-GCP-PERMISSION-PROBE-SCOPE-01-v1",
              "nearest_record_url": "/varexis-index/records/gcp-permission-probe-explicit-caller-resource-scope.json",
              "nearest_record_sha256": "122fcd11de3e1ce004e7fbca74eaca8c947f1a38b18084c40137dd961e38088b",
              "material_distinction": "Documented managed delete wildcards require explicit full-project scope. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-MEM0-FILTERED-DELETE-WILDCARD-SCOPE-01-v1"
              },
              "record_url": "/varexis-index/records/mem0-filtered-delete-wildcard-scope.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Can a Mem0 user wildcard be treated as a complete project erasure? Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.",
            "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#mem0-filtered-delete-wildcard-scope",
          "machine_readable_record": "/varexis-index/records/mem0-filtered-delete-wildcard-scope.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-MEM0-IMMUTABLE-MEMORY-CORRECTION-01-v1",
        "url": "/varexis-index/records/mem0-immutable-memory-correction.json",
        "content_sha256": "674ff33e71ca32e1ca36c13c43fdf6ed78c6e7f10222d4633d8bcfcd8f734a7d",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-MEM0-IMMUTABLE-MEMORY-CORRECTION-01-v1",
          "record_kind": "external_reference",
          "title": "Immutable memory correction requires delete/re-add, with old/new identity linkage",
          "system": "Mem0",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Can a Mem0 immutable memory be corrected with an ordinary update?",
          "near_questions": [
            "Can an immutable Mem0 memory be edited in place?",
            "What identities must be tracked when immutable memory is replaced?",
            "Does delete-and-readd preserve the original Mem0 memory identity?",
            "What evidence links old and replacement immutable memories?"
          ],
          "supported_claims": [
            {
              "claim": "Mem0 documents immutable memories as requiring delete and re-add rather than update. Managed and OSS interfaces report the rejected update differently.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.",
            "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": "Mem0 documents immutable memories as requiring delete and re-add rather than update. Managed and OSS interfaces report the rejected update differently.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Mem0 primary documentation: mem0 update",
            "source_url": "https://docs.mem0.ai/core-concepts/memory-operations/update.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-MEM0-IMMUTABLE-MEMORY-CORRECTION-01-v1",
            "candidate_record_sha256": "40a99c6c0d2aca9cf4fc2fbb59a4945ed516104796b40932f00c330788b529e4",
            "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": "Mem0 documents immutable memories as requiring delete and re-add rather than update. Managed and OSS interfaces report the rejected update differently.",
            "required_buyer_context": "immutable status; original ID; rejected update; delete/add receipts; replacement ID. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Can a Mem0 immutable memory be corrected with an ordinary update?",
            "documented_statement": {
              "status": "documented",
              "statement": "Mem0 documents immutable memories as requiring delete and re-add rather than update. Managed and OSS interfaces report the rejected update differently.",
              "source_ids": [
                "mem0-update-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Can a Mem0 immutable memory be corrected with an ordinary update? Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes. Immutable memory correction requires delete/re-add, with old/new identity linkage. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "mem0-update-md"
              ]
            },
            "buyer_evidence_required": [
              "immutable status",
              "original ID",
              "rejected update",
              "delete/add receipts",
              "replacement ID"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes."
            },
            "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": "mem0-update-md",
                "url": "https://docs.mem0.ai/core-concepts/memory-operations/update.md",
                "final_url": "https://docs.mem0.ai/core-concepts/memory-operations/update.md",
                "captured_at_utc": "2026-10-30T18:29:16.252664+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 6515,
                "sha256": "a7b2baa838ec976006ae34177bd0be565e473bb7ef4b5034d02c701055095eb8",
                "title": "Mem0 primary documentation: mem0 update",
                "publisher": "Mem0",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Immutable memories must be deleted and re-added",
                  "None clears it"
                ]
              }
            ],
            "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": "Can a Mem0 immutable memory be corrected with an ordinary update? Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.",
              "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": "Immutable memories must be deleted and re-added"
            },
            "buyer_relevance": "Can a Mem0 immutable memory be corrected with an ordinary update? Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.",
            "refusal_conditions": [
              "Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Can a Mem0 immutable memory be corrected with an ordinary update?",
              "consequence": "Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B15",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
              "nearest_record_url": "/varexis-index/records/copilot-conversation-deletion-memory-separation.json",
              "nearest_record_sha256": "d50b322fa3e23edbe51363ab32c6eb085bb8c4c200098ad2bde3d095ec511e82",
              "material_distinction": "Immutable memory correction requires delete/re-add, with old/new identity linkage. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-MEM0-IMMUTABLE-MEMORY-CORRECTION-01-v1"
              },
              "record_url": "/varexis-index/records/mem0-immutable-memory-correction.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Can a Mem0 immutable memory be corrected with an ordinary update? Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.",
            "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#mem0-immutable-memory-correction",
          "machine_readable_record": "/varexis-index/records/mem0-immutable-memory-correction.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-MEM0-MULTI-STORE-CUSTODY-INVENTORY-01-v1",
        "url": "/varexis-index/records/mem0-multi-store-custody-inventory.json",
        "content_sha256": "b8f5d142bf66340eedbbd625e5bdb658e457ffc734062895b3201126aecad119",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-MEM0-MULTI-STORE-CUSTODY-INVENTORY-01-v1",
          "record_kind": "external_reference",
          "title": "SQL/vector/entity representations versus single-store exit completeness",
          "system": "Mem0",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Is a Mem0 vector-store export a complete memory custody inventory?",
          "near_questions": [
            "Does a Mem0 custody inventory need more than its vector database?",
            "Which fact entity and vector representations may store memory data?",
            "Can managed Mem0 architecture be assumed for every self-hosted setup?",
            "What deployment scope should a multi-store memory review record?"
          ],
          "supported_claims": [
            {
              "claim": "The reviewed architecture separates facts/metadata in SQL, embeddings in a vector database and extracted entities in an entity store; managed and OSS operation differs.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.",
            "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": "The reviewed architecture separates facts/metadata in SQL, embeddings in a vector database and extracted entities in an entity store; managed and OSS operation differs.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Mem0 primary documentation: mem0 filters",
            "source_url": "https://docs.mem0.ai/core-concepts/memory-types.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-MEM0-MULTI-STORE-CUSTODY-INVENTORY-01-v1",
            "candidate_record_sha256": "d9a34e07a163f256c209e812d3e867bf09e0df42a6fb74ad31524fe531590b21",
            "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": "The reviewed architecture separates facts/metadata in SQL, embeddings in a vector database and extracted entities in an entity store; managed and OSS operation differs.",
            "required_buyer_context": "managed/OSS mode; configured stores; fact/vector/entity inventories; export manifests; residual copies. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Is a Mem0 vector-store export a complete memory custody inventory?",
            "documented_statement": {
              "status": "documented",
              "statement": "The reviewed architecture separates facts/metadata in SQL, embeddings in a vector database and extracted entities in an entity store; managed and OSS operation differs.",
              "source_ids": [
                "mem0-filters-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Is a Mem0 vector-store export a complete memory custody inventory? Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions. SQL/vector/entity representations versus single-store exit completeness. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "mem0-filters-md"
              ]
            },
            "buyer_evidence_required": [
              "managed/OSS mode",
              "configured stores",
              "fact/vector/entity inventories",
              "export manifests",
              "residual copies"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions."
            },
            "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": "mem0-filters-md",
                "url": "https://docs.mem0.ai/core-concepts/memory-types.md",
                "final_url": "https://docs.mem0.ai/core-concepts/how-it-works.md",
                "captured_at_utc": "2026-10-30T18:29:16.577768+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 6263,
                "sha256": "43643261fc6e63a6d742e19be2ff50356152ccef33e05fc0071f3ac0ca8e59a8",
                "title": "Mem0 primary documentation: mem0 filters",
                "publisher": "Mem0",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "automatic extraction path is additive",
                  "Where memories live"
                ]
              }
            ],
            "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": "Is a Mem0 vector-store export a complete memory custody inventory? Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.",
              "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": "Where memories live"
            },
            "buyer_relevance": "Is a Mem0 vector-store export a complete memory custody inventory? Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.",
            "refusal_conditions": [
              "Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Is a Mem0 vector-store export a complete memory custody inventory?",
              "consequence": "Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B16",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-OPENAI-VECTOR-FILE-REMOVAL-UNDERLYING-UPLOAD-RETAINED-01-v1",
              "nearest_record_url": "/varexis-index/records/openai-vector-file-removal-underlying-upload-retained.json",
              "nearest_record_sha256": "58c2f109927a4f7a531dcc3fad5a495638767e08c0448b8edd081192a3a0d127",
              "material_distinction": "SQL/vector/entity representations versus single-store exit completeness. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-MEM0-MULTI-STORE-CUSTODY-INVENTORY-01-v1"
              },
              "record_url": "/varexis-index/records/mem0-multi-store-custody-inventory.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Is a Mem0 vector-store export a complete memory custody inventory? Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.",
            "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#mem0-multi-store-custody-inventory",
          "machine_readable_record": "/varexis-index/records/mem0-multi-store-custody-inventory.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-MEM0-EXPIRY-UPDATE-CLEARING-01-v1",
        "url": "/varexis-index/records/mem0-expiry-update-clearing.json",
        "content_sha256": "4c8fe3d1cc2f5fa27203fe36eefdf6e52c9d80dc931fde7d0e1ad996064280e6",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-MEM0-EXPIRY-UPDATE-CLEARING-01-v1",
          "record_kind": "external_reference",
          "title": "Metadata/expiry-only update can change retention without changing text",
          "system": "Mem0",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Can a Mem0 metadata-only update alter expiry without changing memory text?",
          "near_questions": [
            "Can a Mem0 metadata-only update leave the memory text unchanged?",
            "What happens when Mem0 expiration is updated to null?",
            "Does changing memory metadata automatically renew retention?",
            "Which expiry value must a Mem0 update review preserve?"
          ],
          "supported_claims": [
            {
              "claim": "The documented OSS update accepts metadata and/or expiration changes while retaining text, and explicitly allows clearing expiration with None/null.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.",
            "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": "The documented OSS update accepts metadata and/or expiration changes while retaining text, and explicitly allows clearing expiration with None/null.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Mem0 primary documentation: mem0 update",
            "source_url": "https://docs.mem0.ai/core-concepts/memory-operations/update.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-MEM0-EXPIRY-UPDATE-CLEARING-01-v1",
            "candidate_record_sha256": "e35c57e5335e055f4c45401407941212ce2b9ebd2fa4f8d6e0998f187a2bba88",
            "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": "The documented OSS update accepts metadata and/or expiration changes while retaining text, and explicitly allows clearing expiration with None/null.",
            "required_buyer_context": "SDK version; before/after text hash; expiration and metadata; update payload; approval. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Can a Mem0 metadata-only update alter expiry without changing memory text?",
            "documented_statement": {
              "status": "documented",
              "statement": "The documented OSS update accepts metadata and/or expiration changes while retaining text, and explicitly allows clearing expiration with None/null.",
              "source_ids": [
                "mem0-update-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Can a Mem0 metadata-only update alter expiry without changing memory text? Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy. Metadata/expiry-only update can change retention without changing text. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "mem0-update-md"
              ]
            },
            "buyer_evidence_required": [
              "SDK version",
              "before/after text hash",
              "expiration and metadata",
              "update payload",
              "approval"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy."
            },
            "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": "mem0-update-md",
                "url": "https://docs.mem0.ai/core-concepts/memory-operations/update.md",
                "final_url": "https://docs.mem0.ai/core-concepts/memory-operations/update.md",
                "captured_at_utc": "2026-10-30T18:29:16.252664+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 6515,
                "sha256": "a7b2baa838ec976006ae34177bd0be565e473bb7ef4b5034d02c701055095eb8",
                "title": "Mem0 primary documentation: mem0 update",
                "publisher": "Mem0",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Immutable memories must be deleted and re-added",
                  "None clears it"
                ]
              }
            ],
            "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": "Can a Mem0 metadata-only update alter expiry without changing memory text? Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.",
              "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": "None clears it"
            },
            "buyer_relevance": "Can a Mem0 metadata-only update alter expiry without changing memory text? Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.",
            "refusal_conditions": [
              "Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Can a Mem0 metadata-only update alter expiry without changing memory text?",
              "consequence": "Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B17",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-ICE09-GCP-FEDERATION-MAPPING-CHANGE-EFFECTIVE-PRINCIPAL-01-v1",
              "nearest_record_url": "/varexis-index/records/gcp-federation-mapping-change-effective-principal.json",
              "nearest_record_sha256": "a6ceeb000990e9581e41391aa45d3ce7eba9bd8fdd5c715d9a46b3ec41c1561a",
              "material_distinction": "Metadata/expiry-only update can change retention without changing text. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-MEM0-EXPIRY-UPDATE-CLEARING-01-v1"
              },
              "record_url": "/varexis-index/records/mem0-expiry-update-clearing.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Can a Mem0 metadata-only update alter expiry without changing memory text? Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.",
            "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#mem0-expiry-update-clearing",
          "machine_readable_record": "/varexis-index/records/mem0-expiry-update-clearing.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-LANGGRAPH-CHECKPOINTER-STORE-EXIT-SCOPE-01-v1",
        "url": "/varexis-index/records/langgraph-checkpointer-store-exit-scope.json",
        "content_sha256": "a500cdbb82c996ee43d4ccb9055176edc3bc284924ad12fae82c5d574b7e61db",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-LANGGRAPH-CHECKPOINTER-STORE-EXIT-SCOPE-01-v1",
          "record_kind": "external_reference",
          "title": "Checkpointer thread state versus independent cross-thread store",
          "system": "LangChain",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does removing LangGraph thread state cover its cross-thread memories?",
          "near_questions": [
            "Does deleting a LangGraph thread remove cross-thread store data?",
            "What separates a LangGraph checkpointer from a persistent store?",
            "Can in-memory LangGraph storage establish restart durability?",
            "Which stores belong in a LangGraph application exit inventory?"
          ],
          "supported_claims": [
            {
              "claim": "LangGraph documents checkpointers for thread-scoped graph snapshots and stores for separate cross-thread application data. Applications can use both.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.",
            "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": "LangGraph documents checkpointers for thread-scoped graph snapshots and stores for separate cross-thread application data. Applications can use both.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "LangChain primary documentation: langgraph persistence",
            "source_url": "https://docs.langchain.com/oss/python/langgraph/persistence.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-LANGGRAPH-CHECKPOINTER-STORE-EXIT-SCOPE-01-v1",
            "candidate_record_sha256": "bd78d202d83fb0183c5637f70336e893ac6de55cdee78bc3901c34a9b5c866b0",
            "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": "LangGraph documents checkpointers for thread-scoped graph snapshots and stores for separate cross-thread application data. Applications can use both.",
            "required_buyer_context": "checkpointer implementation; thread IDs; store implementation/namespaces; deletion/export evidence. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does removing LangGraph thread state cover its cross-thread memories?",
            "documented_statement": {
              "status": "documented",
              "statement": "LangGraph documents checkpointers for thread-scoped graph snapshots and stores for separate cross-thread application data. Applications can use both.",
              "source_ids": [
                "langgraph-persistence-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does removing LangGraph thread state cover its cross-thread memories? Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces. Checkpointer thread state versus independent cross-thread store. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "langgraph-persistence-md"
              ]
            },
            "buyer_evidence_required": [
              "checkpointer implementation",
              "thread IDs",
              "store implementation/namespaces",
              "deletion/export evidence"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces."
            },
            "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": "langgraph-persistence-md",
                "url": "https://docs.langchain.com/oss/python/langgraph/persistence.md",
                "final_url": "https://docs.langchain.com/oss/python/langgraph/persistence.md",
                "captured_at_utc": "2026-10-30T18:29:15.853202+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 5321,
                "sha256": "9985e697f3f56c9c703360f75d7e56c0d3040307d46ccff4b0a7d4964ab07932",
                "title": "LangChain primary documentation: langgraph persistence",
                "publisher": "LangChain",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Checkpointer vs. store"
                ]
              }
            ],
            "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": "Does removing LangGraph thread state cover its cross-thread memories? Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.",
              "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": "Checkpointer vs. store"
            },
            "buyer_relevance": "Does removing LangGraph thread state cover its cross-thread memories? Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.",
            "refusal_conditions": [
              "Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does removing LangGraph thread state cover its cross-thread memories?",
              "consequence": "Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B18",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-ICE08-LANGSMITH-THREAD-CHILD-METADATA-COST-OMISSION-01-v1",
              "nearest_record_url": "/varexis-index/records/langsmith-thread-child-metadata-cost-omission.json",
              "nearest_record_sha256": "9f66c7051fb7142cb26f146c4221d18e0b6588b2a3f559362e149a232bf0c1aa",
              "material_distinction": "Checkpointer thread state versus independent cross-thread store. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-LANGGRAPH-CHECKPOINTER-STORE-EXIT-SCOPE-01-v1"
              },
              "record_url": "/varexis-index/records/langgraph-checkpointer-store-exit-scope.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does removing LangGraph thread state cover its cross-thread memories? Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.",
            "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#langgraph-checkpointer-store-exit-scope",
          "machine_readable_record": "/varexis-index/records/langgraph-checkpointer-store-exit-scope.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-MS-HARNESS-LOCAL-MANAGED-MEMORY-CUSTODY-01-v1",
        "url": "/varexis-index/records/ms-harness-local-managed-memory-custody.json",
        "content_sha256": "ac8bd662d10e50a3eef7fb8a383f34605e9b7b7461da575816e1f090f93af708",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-MS-HARNESS-LOCAL-MANAGED-MEMORY-CUSTODY-01-v1",
          "record_kind": "external_reference",
          "title": "Local harness file memory versus opt-in managed Foundry facts",
          "system": "Microsoft",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts?",
          "near_questions": [
            "Does local Microsoft harness memory share the same custody as managed Foundry memory?",
            "Can explicit file memory and automatic extracted facts coexist?",
            "What should distinguish local and managed memory in a harness inventory?",
            "Does removing a session folder establish disposal of managed facts?"
          ],
          "supported_claims": [
            {
              "claim": "Microsoft distinguishes agent-written local file memory from automatically extracted managed Foundry memory. The two can be used together and have different storage and scope.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.",
            "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": "Microsoft distinguishes agent-written local file memory from automatically extracted managed Foundry memory. The two can be used together and have different storage and scope.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "Microsoft primary documentation: ms harness memory",
            "source_url": "https://devblogs.microsoft.com/agent-framework/agent-harness-working-with-your-data-safely/",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-MS-HARNESS-LOCAL-MANAGED-MEMORY-CUSTODY-01-v1",
            "candidate_record_sha256": "262cdac15e6efefc4b8bb7ce2330b6a9b707f61f1b4367b2be7f9a75be45efef",
            "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": "Microsoft distinguishes agent-written local file memory from automatically extracted managed Foundry memory. The two can be used together and have different storage and scope.",
            "required_buyer_context": "provider configuration; local folder/session mapping; Foundry store/user scope; separate deletion evidence. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts?",
            "documented_statement": {
              "status": "documented",
              "statement": "Microsoft distinguishes agent-written local file memory from automatically extracted managed Foundry memory. The two can be used together and have different storage and scope.",
              "source_ids": [
                "ms-harness-memory"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts? Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts. Local harness file memory versus opt-in managed Foundry facts. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "ms-harness-memory"
              ]
            },
            "buyer_evidence_required": [
              "provider configuration",
              "local folder/session mapping",
              "Foundry store/user scope",
              "separate deletion evidence"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts."
            },
            "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": "ms-harness-memory",
                "url": "https://devblogs.microsoft.com/agent-framework/agent-harness-working-with-your-data-safely/",
                "final_url": "https://devblogs.microsoft.com/agent-framework/agent-harness-working-with-your-data-safely/",
                "captured_at_utc": "2026-10-30T18:28:07.199052+00:00",
                "status": 200,
                "content_type": "text/html; charset=UTF-8",
                "bytes": 268712,
                "sha256": "bb075eb6d1d240c8e3899052a6bb05a2f31913691048af252c64b4b2e360cd32",
                "title": "Microsoft primary documentation: ms harness memory",
                "publisher": "Microsoft",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "File memory (coarse, explicit)"
                ]
              }
            ],
            "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": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts? Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.",
              "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": "File memory (coarse, explicit)"
            },
            "buyer_relevance": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts? Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.",
            "refusal_conditions": [
              "Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts?",
              "consequence": "Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B20",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-EVENT-DELETE-DERIVED-MEMORY-RESIDUE-01-v1",
              "nearest_record_url": "/varexis-index/records/agentcore-event-delete-derived-memory-residue.json",
              "nearest_record_sha256": "240ae602db6e63a80b00e3ac83e9f384479e7a89b7dc19679e92a20ea1f579b4",
              "material_distinction": "Local harness file memory versus opt-in managed Foundry facts. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-MS-HARNESS-LOCAL-MANAGED-MEMORY-CUSTODY-01-v1"
              },
              "record_url": "/varexis-index/records/ms-harness-local-managed-memory-custody.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts? Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.",
            "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#ms-harness-local-managed-memory-custody",
          "machine_readable_record": "/varexis-index/records/ms-harness-local-managed-memory-custody.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-OPENAI-MOUNTED-SKILL-EXPIRY-ASSET-RETENTION-01-v1",
        "url": "/varexis-index/records/openai-mounted-skill-expiry-asset-retention.json",
        "content_sha256": "735f403e9d76d11d6bb3970d82d15773640a17da97a38b23115dd3ca243769b5",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-OPENAI-MOUNTED-SKILL-EXPIRY-ASSET-RETENTION-01-v1",
          "record_kind": "external_reference",
          "title": "Mounted container-file lifetime versus separately managed uploaded skill assets",
          "system": "OpenAI",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset?",
          "near_questions": [
            "Does expiry of an OpenAI container delete its uploaded skill asset?",
            "What retention boundary separates mounted files and hosted skill versions?",
            "Can temporary skill file disappearance prove source-asset deletion?",
            "Which asset identifiers remain relevant after a skill container expires?"
          ],
          "supported_claims": [
            {
              "claim": "The guide binds mounted skills and container files to the hosted container lifecycle, while separately describing uploaded skill versions and their deletion rules.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.",
            "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": "The guide binds mounted skills and container files to the hosted container lifecycle, while separately describing uploaded skill versions and their deletion rules.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "OpenAI primary documentation: openai skills",
            "source_url": "https://developers.openai.com/api/docs/guides/tools-skills.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-OPENAI-MOUNTED-SKILL-EXPIRY-ASSET-RETENTION-01-v1",
            "candidate_record_sha256": "21c72250243ecf1f7a334fe42396e857ac07eb28bc223d26fefbab0c9e3b47fc",
            "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": "The guide binds mounted skills and container files to the hosted container lifecycle, while separately describing uploaded skill versions and their deletion rules.",
            "required_buyer_context": "container ID/lifecycle; uploaded skill/version IDs; copied files; asset deletion receipts; output inventory. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset?",
            "documented_statement": {
              "status": "documented",
              "statement": "The guide binds mounted skills and container files to the hosted container lifecycle, while separately describing uploaded skill versions and their deletion rules.",
              "source_ids": [
                "openai-skills"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset? Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence. Mounted container-file lifetime versus separately managed uploaded skill assets. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "openai-skills"
              ]
            },
            "buyer_evidence_required": [
              "container ID/lifecycle",
              "uploaded skill/version IDs",
              "copied files",
              "asset deletion receipts",
              "output inventory"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence."
            },
            "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": "openai-skills",
                "url": "https://developers.openai.com/api/docs/guides/tools-skills.md",
                "final_url": "https://developers.openai.com/api/docs/guides/tools-skills.md",
                "captured_at_utc": "2026-10-30T18:22:05.728535+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 27483,
                "sha256": "4867f4730153483516f3732506208e014edad959ff31105409041a67c2dc3224",
                "title": "OpenAI primary documentation: openai skills",
                "publisher": "OpenAI",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "Version pointers",
                  "Wait for an uploaded version",
                  "Use skills with local shell mode",
                  "Capability directories have these requirements",
                  "Delete rules",
                  "Validate data residency and retention requirements"
                ]
              }
            ],
            "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": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset? Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.",
              "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": "Validate data residency and retention requirements"
            },
            "buyer_relevance": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset? Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.",
            "refusal_conditions": [
              "Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset?",
              "consequence": "Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B21",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-OWASP-AGENTIC-SKILLS-02-v1",
              "nearest_record_url": "/varexis-index/records/agent-skills-versus-mcp-security-scope.json",
              "nearest_record_sha256": "5beaf7612c4b900f27b52040915a5bfe3f587be2c142793782215ead7ed10147",
              "material_distinction": "Mounted container-file lifetime versus separately managed uploaded skill assets. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-OPENAI-MOUNTED-SKILL-EXPIRY-ASSET-RETENTION-01-v1"
              },
              "record_url": "/varexis-index/records/openai-mounted-skill-expiry-asset-retention.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset? Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.",
            "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#openai-mounted-skill-expiry-asset-retention",
          "machine_readable_record": "/varexis-index/records/openai-mounted-skill-expiry-asset-retention.json"
        }
      },
      {
        "record_id": "VXI-EXT-ICE10-LANGGRAPH-BACKGROUND-MEMORY-FRESHNESS-01-v1",
        "url": "/varexis-index/records/langgraph-background-memory-freshness.json",
        "content_sha256": "710129c98ae89837389b60e14de457d0a143862302eb9b0e1df2cd7196294964",
        "evidence": {
          "schema": "varexis-public-evidence-record/0.3",
          "generated_at_utc": "2026-10-30T18:53:33.881Z",
          "record_id": "VXI-EXT-ICE10-LANGGRAPH-BACKGROUND-MEMORY-FRESHNESS-01-v1",
          "record_kind": "external_reference",
          "title": "Background long-term memory write completion versus response completion; distinct from checkpoint durability modes",
          "system": "LangChain",
          "evidence_family": "vendor_evidence_review",
          "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
          "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
          "canonical_question": "Does an agent response establish that its background memory write has finished?",
          "near_questions": [
            "Does a completed LangGraph turn prove background memory extraction is complete?",
            "How do hot-path and background memory writes differ in visibility?",
            "What unfinished work can affect a LangGraph memory exit inventory?",
            "Can retrieval immediately after a turn establish complete long-term memory?"
          ],
          "supported_claims": [
            {
              "claim": "The LangGraph guide distinguishes memory writes in the request path from background/asynchronous updates with different timing and complexity.",
              "reliance": "DOCUMENTED_CAPABILITY_ONLY"
            }
          ],
          "not_demonstrated_claims": [
            "Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.",
            "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": "The LangGraph guide distinguishes memory writes in the request path from background/asynchronous updates with different timing and complexity.",
          "related_record_ids": [],
          "source_review": {
            "source_type": "official_external_documentation",
            "source_title": "LangChain primary documentation: langgraph memory",
            "source_url": "https://docs.langchain.com/oss/python/langgraph/memory.md",
            "checked_on": "2026-10-30",
            "candidate_record_id": "VXI-EXT-ICE10-LANGGRAPH-BACKGROUND-MEMORY-FRESHNESS-01-v1",
            "candidate_record_sha256": "4db8455809f88c9f79bb81d36a63eb6ba20504b1c7b748d47bbf0e5e2bf707c9",
            "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": "The LangGraph guide distinguishes memory writes in the request path from background/asynchronous updates with different timing and complexity.",
            "required_buyer_context": "write mode; job/request correlation; completion state; stored IDs; dependent retrieval check. 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",
            "applicability_status": "Primary rolling documentation captured 2026-10-30; runtime/version applicability must be checked before reliance. No buyer deployment was inspected.",
            "checked_on": "2026-10-30",
            "claim_to_check": "Does an agent response establish that its background memory write has finished?",
            "documented_statement": {
              "status": "documented",
              "statement": "The LangGraph guide distinguishes memory writes in the request path from background/asynchronous updates with different timing and complexity.",
              "source_ids": [
                "langgraph-memory-md"
              ]
            },
            "review_inference": {
              "status": "review_inference",
              "statement": "Does an agent response establish that its background memory write has finished? Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions. Background long-term memory write completion versus response completion; distinct from checkpoint durability modes. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.",
              "source_ids": [
                "langgraph-memory-md"
              ]
            },
            "buyer_evidence_required": [
              "write mode",
              "job/request correlation",
              "completion state",
              "stored IDs",
              "dependent retrieval check"
            ],
            "review_condition": {
              "status": "varexis_review_policy",
              "statement": "Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions."
            },
            "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": "langgraph-memory-md",
                "url": "https://docs.langchain.com/oss/python/langgraph/memory.md",
                "final_url": "https://docs.langchain.com/oss/python/concepts/memory.md",
                "captured_at_utc": "2026-10-30T18:29:16.016909+00:00",
                "status": 200,
                "content_type": "text/markdown; charset=utf-8",
                "bytes": 20191,
                "sha256": "7cba0710f88942a51b1b5024a27825270afb951db98727035a1a10cdd6583922",
                "title": "LangChain primary documentation: langgraph memory",
                "publisher": "LangChain",
                "checked_on": "2026-10-30",
                "capture_status": 200,
                "claim_review_completed": true,
                "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
                "version_context": "Rolling primary documentation captured 2026-10-30. The capture pins source bytes, not a provider runtime release; verify the installed version and configuration.",
                "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
                "reviewed_sections": [
                  "In the background"
                ]
              }
            ],
            "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": "Does an agent response establish that its background memory write has finished? Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.",
              "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": "In the background"
            },
            "buyer_relevance": "Does an agent response establish that its background memory write has finished? Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.",
            "refusal_conditions": [
              "Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.",
              "Do not infer deployment conformance, authority or successful outcomes from source documentation."
            ],
            "decision_context": {
              "operator": "Memory custody reviewer",
              "scenario": "Does an agent response establish that its background memory write has finished?",
              "consequence": "Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.",
              "confidence": "Primary documentation supports the narrow stated distinction; deployment conformance and purchase demand remain unestablished."
            },
            "novelty_review": {
              "candidate_id": "ICE10-B22",
              "disposition": "distinct_operational_decision",
              "nearest_record_id": "VXI-EXT-AWS-AC-MEM-01-v1",
              "nearest_record_url": "/varexis-index/records/aws-agentcore-memory-scope.json",
              "nearest_record_sha256": "b010d3601d6ebf87833b222aa4108533379e0bf1a17806b1a83a7131bab67016",
              "material_distinction": "Background long-term memory write completion versus response completion; distinct from checkpoint durability modes. The decision turns on the documented operation and required evidence, not on a different vendor name.",
              "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
            },
            "optional_selection": {
              "guide_id": null,
              "guide_url": null,
              "guide_manifest": "/varexis-index/decision-guides.json",
              "checker": {
                "product_id": "agent-data-exit",
                "price_gbp_excluding_vat": 79,
                "purchase_url": "/index-access?route=agentic_pack_data_exit_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": "The existing checker does not connect to this platform or execute these review worksheets. Use it only for its already-supported supplied declaration schema and separate licence."
            },
            "exact_access": {
              "endpoint": "/mcp/catalogue",
              "tool": "get_publication_record",
              "arguments": {
                "record_id": "VXI-EXT-ICE10-LANGGRAPH-BACKGROUND-MEMORY-FRESHNESS-01-v1"
              },
              "record_url": "/varexis-index/records/langgraph-background-memory-freshness.json",
              "original_mcp_search": false,
              "paid_saved_retrieval": false
            }
          },
          "niche": {
            "niche_id": "ice10-custody",
            "label": "AI Data Custody, Retention & Exit Assurance",
            "classification_id": "custody",
            "classification_label": "AI Data Custody, Retention & Exit Assurance",
            "topic_id": "custody",
            "buyer_intent": "Does an agent response establish that its background memory write has finished? Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.",
            "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#langgraph-background-memory-freshness",
          "machine_readable_record": "/varexis-index/records/langgraph-background-memory-freshness.json"
        }
      }
    ],
    "basis": "VAREXIS-authored editable review documents and a completed synthetic example. Source documentation is dated context; no provider or buyer deployment is inspected.",
    "boundary": "GBP 19 plus applicable VAT, one-time internal-use licence for this exact version. No executable licence, subscription, saved evidence receipt, future update, monitoring, resale or SLA. No live inspection, discovery of unknown copies, actual deletion verification, legal assessment, certification or automated analysis.",
    "paid_artifact": {
      "schema": "varexis-operator-artifact/1",
      "filename": "varexis-memory-custody-operator-v1.zip",
      "media_type": "application/zip",
      "encoding": "base64",
      "archive_sha256": "81e75c3469260e6bd33feeaeb5a4744df3ae901d85341327c23e0317bd33f3c1",
      "manifest_sha256": "58d050c0db2fe9a8d1df3eb5ee3648e18e15af245cb10214943fa6f2d30a2436",
      "bytes": 16736,
      "runtime": "Local CSV/JSON/Markdown editor; manual review, no executable",
      "licence": "VAREXIS Agent Memory & Context Custody Operator Pack v1.0.0\r\nOne-time internal-use licence for one purchasing individual or one legal entity, including staff and agents acting internally on its behalf. The purchaser may copy, complete and adapt these VAREXIS-authored review templates for internal decisions without a per-use fee. Completed internal decision records may be shared with the purchaser’s own reviewers and auditors for that decision; this does not grant redistribution or resale of the reusable template library. No sublicensing, template redistribution, hosted customer service, API resale, external agent distribution, executable checker licence, future updates, monitoring or support SLA is included. Public source evidence retains its existing terms; this licence does not relicense third-party documentation. Billing and delivery support follows https://varexis.tech/checkout-terms. Statutory rights are unaffected. Rights begin only after provider-verified payment for this exact product. Retain the original purchase key for authenticated delivery and recovery.\r\n",
      "extract_and_run": "Extract the ZIP and start with README.md; complete templates manually against authorised supplied evidence."
    },
    "snapshot_sha256": "879f92c97659865ecfdc8c0de8ad0fa3e69b25e63f1b10f0a69cf1d2b5f24150",
    "preview_kind": "paid_operator_manifest",
    "preview_payload_sha256": "14d6c2a82f3e867002339d6d23fdc03198abad019b045cfeea8a6e85e55cd41c"
  }
}
