{ "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-14T20:21:57.226Z", "route_id": "agentic_pack_evidence_boundary_audit_v1", "question": "Audit and export evidence?", "answer": "Review what an activity-history claim can establish before using it in a technical review or procurement discussion. This pack compares the existing GitHub audit, Slack export and Cloudflare Logpush documentation reviews dated 14 October 2026. It preserves event and conversation scope, required buyer evidence, retention and delivery gaps, and conditions for withholding broader conclusions. Missing records do not establish that nothing happened; no buyer export or deployment has been inspected.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1", "url": "/varexis-index/records/github-audit-export-evidence-check.json", "content_sha256": "d89252d2c9a5cf877e4f79474442b150565ac2760e6b2c5e5a2d94201f0fc1ec", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-13T23:52:59.204Z", "record_id": "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1", "record_kind": "external_reference", "title": "GitHub audit evidence: Event coverage and export history", "system": "GitHub Enterprise Cloud", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does a GitHub audit export establish a complete history of repository activity?", "near_questions": [ "Does a GitHub audit export include every Git operation?", "Which GitHub audit events are visible through the web interface?", "Does GitHub audit API access depend on the plan?", "Are GitHub web and Git events retained equally?", "Can a missing GitHub audit event prove nothing happened?", "What query parameters should accompany a GitHub audit export?", "Does a streamed GitHub archive establish continuous capture?", "Which organization role can obtain GitHub audit evidence?", "What evidence supports a claimed repository activity timeline?", "Can browser-triggered Git activity be missing from a Git export?", "What should I save alongside a GitHub audit-history review?", "When does a GitHub export need a coverage qualification?" ], "supported_claims": [ { "claim": "GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Verified buyer configuration or effective access rights", "Independent execution, completeness or security testing", "Vendor certification, legal compliance or guaranteed suitability" ], "public_summary": "GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.", "related_record_ids": [ "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1", "VXI-EXT-PROCUREMENT-VERCEL-AUDIT-01-v1", "VXI-EXT-PROCUREMENT-STRIPE-WEBHOOK-01-v1", "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "GitHub organization audit access and retention", "source_url": "https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization", "checked_on": "2026-10-14", "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1", "candidate_record_sha256": "6e5a255316951dcab1bd8cf62f308fc80033b13caf0ab68405fb31e5fa5e85ad", "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": "GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.", "required_buyer_context": "Organization plan, export method, event types, requested interval and any external streaming archive.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "decision_profile": { "schema": "varexis-vendor-evidence-review/1", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "claim_to_check": "An audit export contains every repository action needed for this review.", "documented_statement": { "status": "documented", "statement": "GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.", "source_ids": [ "github-audit" ] }, "buyer_evidence_required": [ "A dated export showing its query and event categories", "Plan entitlement and exporter role", "Streaming-destination continuity and retention, if longer history is required" ], "review_condition": { "status": "varexis_review_policy", "statement": "Require additional evidence when the needed event type or time range is outside the demonstrated export coverage." }, "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.", "evidence_sources": [ { "source_id": "github-audit", "url": "https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization", "final_url": "https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization", "title": "GitHub organization audit access and retention", "checked_on": "2026-10-14", "sha256": "fd60047bcbad42fe0a972ab0cf6a2d176b33d1f839ab9a9125b66df66de9b8b4", "bytes": 442192 } ], "observed_deployment": false, "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.", "paid_value": { "decision_context": "Preserve why an activity-history claim was limited to a specific export method and interval.", "free": "Complete review, practical questions, sources and limitations; may be saved locally.", "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.", "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.", "excluded": [ "Fresh vendor research", "Continuous monitoring or change alerts", "Testing the buyer configuration", "Private evidence or vendor certification" ], "integrity": "Hashes identify content versions; they do not prove truth or provide a signature." }, "revalidation": { "trigger": "A saved purchase does not recheck the source or buyer configuration.", "specific_watch": "Recheck plan, available event categories, export method and archive retention." } }, "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#github-audit-export-evidence-check", "machine_readable_record": "/varexis-index/records/github-audit-export-evidence-check.json" } }, { "record_id": "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1", "url": "/varexis-index/records/slack-export-plan-coverage-check.json", "content_sha256": "c52149c23db71f8def7ee6d6fea394f19380c6a4a74aa2322b65ae438a1b8fe1", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-13T23:52:59.204Z", "record_id": "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1", "record_kind": "external_reference", "title": "Slack export evidence: Plan and conversation coverage", "system": "Slack", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does a Slack workspace export contain private channels, direct messages and the files themselves?", "near_questions": [ "Do all Slack plans export private channels?", "Are Slack direct messages included in a public-channel export?", "Does a Slack export contain file bytes or file links?", "Who must approve a broader Slack export?", "Does Slack export availability establish permission to collect every conversation?", "What retention settings affect Slack export completeness?", "Can an expired file link leave a Slack evidence gap?", "What plan evidence should accompany a Slack export?", "Can an agent label a Slack export complete without checking conversation types?", "What is missing from a public-only Slack archive?", "What should be preserved for a Slack migration evidence review?", "When should a Slack export scope be rechecked?" ], "supported_claims": [ { "claim": "Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Verified buyer configuration or effective access rights", "Independent execution, completeness or security testing", "Vendor certification, legal compliance or guaranteed suitability" ], "public_summary": "Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.", "related_record_ids": [ "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1", "VXI-EXT-PROCUREMENT-VERCEL-AUDIT-01-v1", "VXI-EXT-PROCUREMENT-STRIPE-WEBHOOK-01-v1", "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "Slack workspace export eligibility and coverage", "source_url": "https://slack.com/help/articles/201658943-export-your-workspace-data", "checked_on": "2026-10-14", "candidate_record_id": "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1", "candidate_record_sha256": "9f45b11244a337bf0d9587c588baf1c77ffa4f9cdb74c7d50f9e66a190a7c08b", "method": "Primary documentation reviewed for the published bounded statement.", "deployment_tested_by_varexis": false, "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research." }, "answer_policy": { "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY", "bounded_answer": "Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.", "required_buyer_context": "Workspace plan, approved export type, requesting role, retention settings and attachment retrieval method.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "decision_profile": { "schema": "varexis-vendor-evidence-review/1", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "claim_to_check": "This Slack export is a complete copy of all workspace conversations and attachments.", "documented_statement": { "status": "documented", "statement": "Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.", "source_ids": [ "slack-export" ] }, "buyer_evidence_required": [ "Export eligibility and any required approval", "A dated export manifest identifying conversation scope", "Evidence that needed file contents were retained separately from links" ], "review_condition": { "status": "varexis_review_policy", "statement": "Qualify completeness if private conversations, retention periods or linked file contents are not accounted for." }, "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.", "evidence_sources": [ { "source_id": "slack-export", "url": "https://slack.com/help/articles/201658943-export-your-workspace-data", "final_url": "https://slack.com/intl/en-gb/help/articles/201658943-export-your-workspace-data", "title": "Slack workspace export eligibility and coverage", "checked_on": "2026-10-14", "sha256": "f07286daa54dbcd09eecd8c6a6d78206578837f05ce1a4b73f2ac9966e0e85ef", "bytes": 104626 } ], "observed_deployment": false, "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.", "paid_value": { "decision_context": "Retain the export-scope limitations behind a workspace review or migration decision.", "free": "Complete review, practical questions, sources and limitations; may be saved locally.", "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.", "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.", "excluded": [ "Fresh vendor research", "Continuous monitoring or change alerts", "Testing the buyer configuration", "Private evidence or vendor certification" ], "integrity": "Hashes identify content versions; they do not prove truth or provide a signature." }, "revalidation": { "trigger": "A saved purchase does not recheck the source or buyer configuration.", "specific_watch": "Recheck plan, export approval, conversation scope and link availability." } }, "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.", "service_route": { "request_guide": "/varexis-index/request.html", "request_workflow": "/varexis-index/request-workflow.json", "service_id": "single_request", "service_routes_url": "/varexis-index/service-routes.json", "payment_required": true, "availability_endpoint": "/api/index/capabilities", "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED", "checkout_url": "/index-access" }, "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.", "human_page": "/varexis-index/catalog.html#slack-export-plan-coverage-check", "machine_readable_record": "/varexis-index/records/slack-export-plan-coverage-check.json" } }, { "record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1", "url": "/varexis-index/records/cloudflare-logpush-history-evidence-check.json", "content_sha256": "6108e7baeeeeffb84770876bd0ff3e401a10df83edc1e6124aaf5138550fe973", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-13T23:52:59.204Z", "record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1", "record_kind": "external_reference", "title": "Cloudflare Logpush evidence: Delivery gaps and retained history", "system": "Cloudflare Logpush", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does enabling Cloudflare Logpush provide a complete searchable archive of past activity?", "near_questions": [ "Does Cloudflare Logpush store logs for later search?", "Can Logpush backfill events from before it was enabled?", "What happens to logs while a Cloudflare Logpush job fails?", "Does an empty Logpush archive prove no traffic occurred?", "Which Cloudflare dataset was actually exported?", "Can Logpush filters omit events needed for a review?", "What evidence proves a Logpush destination retained the data?", "Does Cloudflare product availability determine Logpush dataset access?", "Should an agent check delivery health before interpreting missing logs?", "Can destination retention shorten a Cloudflare activity timeline?", "What should a Logpush evidence-review snapshot retain?", "When does a changed Logpush destination require another review?" ], "supported_claims": [ { "claim": "Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Verified buyer configuration or effective access rights", "Independent execution, completeness or security testing", "Vendor certification, legal compliance or guaranteed suitability" ], "public_summary": "Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.", "related_record_ids": [ "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1", "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1", "VXI-EXT-PROCUREMENT-VERCEL-AUDIT-01-v1", "VXI-EXT-PROCUREMENT-STRIPE-WEBHOOK-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "Cloudflare Logpush storage and delivery scope", "source_url": "https://developers.cloudflare.com/logs/logpush/", "checked_on": "2026-10-14", "candidate_record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1", "candidate_record_sha256": "a47b2419fe274b053e24c833c3cd81cf23ac31c4cf4aeeb56f2a128aac7cd696", "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 describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.", "required_buyer_context": "Dataset, filters, job activation and health, receiving destination and retention policy.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "decision_profile": { "schema": "varexis-vendor-evidence-review/1", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "claim_to_check": "Turning on Logpush creates a complete retained history, including earlier gaps.", "documented_statement": { "status": "documented", "statement": "Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.", "source_ids": [ "cloudflare-logpush" ] }, "buyer_evidence_required": [ "Job configuration showing dataset and filters", "Delivery-health history covering the claimed interval", "Destination receipt and retention evidence for the records being relied on" ], "review_condition": { "status": "varexis_review_policy", "statement": "Qualify the history when delivery or retention is unproven; do not infer a clean incident history from missing logs." }, "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.", "evidence_sources": [ { "source_id": "cloudflare-logpush", "url": "https://developers.cloudflare.com/logs/logpush/", "final_url": "https://developers.cloudflare.com/logs/logpush/", "title": "Cloudflare Logpush storage and delivery scope", "checked_on": "2026-10-14", "sha256": "8c437cfe7cd067c4161fb4601064f1d5b8797c7b70d91f43fd1b0ba8edfd7188", "bytes": 120894 } ], "observed_deployment": false, "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.", "paid_value": { "decision_context": "Retain the capture and retention gaps behind a logging-completeness claim.", "free": "Complete review, practical questions, sources and limitations; may be saved locally.", "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.", "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.", "excluded": [ "Fresh vendor research", "Continuous monitoring or change alerts", "Testing the buyer configuration", "Private evidence or vendor certification" ], "integrity": "Hashes identify content versions; they do not prove truth or provide a signature." }, "revalidation": { "trigger": "A saved purchase does not recheck the source or buyer configuration.", "specific_watch": "Recheck job health, dataset availability, filters and destination retention." } }, "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-logpush-history-evidence-check", "machine_readable_record": "/varexis-index/records/cloudflare-logpush-history-evidence-check.json" } } ], "basis": "A frozen compilation of existing public documentation reviews and their source bindings. No new source review, tool execution, independent experiment or buyer assessment was performed for this package.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material. The saved pack is not continually refreshed. Hashes bind its contents; the optional delivery receipt is unsigned.", "pack": { "schema": "varexis-index-evidence-pack/1", "pack_id": "evidence-boundary-audit", "version": "1.0.0", "title": "Evidence Boundary Pack — Audit & Export Coverage", "prepared_at_utc": "2026-10-15T21:24:49.826Z", "review_status": "documentation_review_only", "source_checked_on": [ "2026-10-14" ], "source_capture_date": null, "source_capture_boundary": "Existing dated review and upstream hash metadata are preserved. No new source bytes were acquired for this compilation; separate capture timestamps and independently tested runtime versions are not established.", "summary_markdown": "# Evidence Boundary Pack — Audit & Export Coverage\n\nUse this package to qualify a claim that an export or log feed provides a complete activity history. Each source answers a different part of the question: GitHub event coverage and interval, Slack conversation and file scope, and Cloudflare delivery and retained history. It is a comparison of documentation boundaries, not a completeness assessment of a supplied archive.\n\n## GitHub audit evidence: Event coverage and export history\nGitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.\n\nRequired context: Organization plan, export method, event types, requested interval and any external streaming archive.\n\nEvidence still needed: A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state.\n\n## Slack export evidence: Plan and conversation coverage\nSlack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.\n\nRequired context: Workspace plan, approved export type, requesting role, retention settings and attachment retrieval method.\n\nEvidence still needed: A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state.\n\n## Cloudflare Logpush evidence: Delivery gaps and retained history\nCloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.\n\nRequired context: Dataset, filters, job activation and health, receiving destination and retention policy.\n\nEvidence still needed: A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state.\n\n## What payment adds\nThe complete package is free to inspect or save locally. Single Request saves this version-bound JSON as one retrievable result. Evidence Receipt also adds the existing unsigned delivery receipt. Eligible subscriptions use one query for the whole pack; retries retain the original request reference and do not consume another query. Keep the access key to recover the saved result.\n\n## Scope\nThe included reviews retain their original dates, findings, unresolved questions and suggested refusal conditions. No fresh research, buyer configuration review, legal conclusion, certification, continual refresh or permanent-retention commitment is included.\n", "comparison": [ { "record_id": "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1", "subject": "GitHub Enterprise Cloud", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "claim_to_check": "An audit export contains every repository action needed for this review.", "documented_statement": { "status": "documented", "statement": "GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.", "source_ids": [ "github-audit" ] }, "buyer_evidence_required": [ "A dated export showing its query and event categories", "Plan entitlement and exporter role", "Streaming-destination continuity and retention, if longer history is required" ], "review_condition": { "status": "varexis_review_policy", "statement": "Require additional evidence when the needed event type or time range is outside the demonstrated export coverage." }, "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature." }, { "record_id": "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1", "subject": "Slack", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "claim_to_check": "This Slack export is a complete copy of all workspace conversations and attachments.", "documented_statement": { "status": "documented", "statement": "Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.", "source_ids": [ "slack-export" ] }, "buyer_evidence_required": [ "Export eligibility and any required approval", "A dated export manifest identifying conversation scope", "Evidence that needed file contents were retained separately from links" ], "review_condition": { "status": "varexis_review_policy", "statement": "Qualify completeness if private conversations, retention periods or linked file contents are not accounted for." }, "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature." }, { "record_id": "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1", "subject": "Cloudflare Logpush", "review_status": "documentation_review_only", "checked_on": "2026-10-14", "claim_to_check": "Turning on Logpush creates a complete retained history, including earlier gaps.", "documented_statement": { "status": "documented", "statement": "Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.", "source_ids": [ "cloudflare-logpush" ] }, "buyer_evidence_required": [ "Job configuration showing dataset and filters", "Delivery-health history covering the claimed interval", "Destination receipt and retention evidence for the records being relied on" ], "review_condition": { "status": "varexis_review_policy", "statement": "Qualify the history when delivery or retention is unproven; do not infer a clean incident history from missing logs." }, "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature." } ], "members": [ { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-14T20:21:57.226Z", "route_id": "agentic_reviewed_github_audit_export_evidence_check", "question": "Does a GitHub audit export establish a complete history of repository activity?", "answer": "GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "ba7380e9ef27473ab3484b562b10185296c88d6117e4ed2147f81d78ace91bbc", "record_ids": [ "VXI-EXT-PROCUREMENT-GITHUB-AUDIT-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-14T20:21:57.226Z", "route_id": "agentic_reviewed_slack_export_plan_coverage_check", "question": "Does a Slack workspace export contain private channels, direct messages and the files themselves?", "answer": "Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "c2b1231e7acc36ad2a0465589f1dcb25589c2cefe251856f297691a564d8ab14", "record_ids": [ "VXI-EXT-PROCUREMENT-SLACK-EXPORT-01-v1" ] }, { "schema": "varexis-index-delivery/1", "catalog_version": "2026-10-14T20:21:57.226Z", "route_id": "agentic_reviewed_cloudflare_logpush_history_evidence_check", "question": "Does enabling Cloudflare Logpush provide a complete searchable archive of past activity?", "answer": "Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.", "basis": "A saved snapshot of the reviewed public route and source records. No fresh source review, independent experiment, deployment assessment or bespoke claim analysis is performed by this delivery.", "boundary": "Public answers remain free. Payment provides automatic retrieval, version binding and a saved delivery. It does not upgrade evidence or disclose protected material.", "snapshot_sha256": "23f58e6f4a80892d02db2b65786d9b0f7c84e3a2ca26da2be1d7f10d779a2092", "record_ids": [ "VXI-EXT-PROCUREMENT-CLOUDFLARE-LOGPUSH-01-v1" ] } ], "rights_review": { "reviewed_on": "2026-10-15", "scope": "This exact public compilation of VAREXIS-authored review prose, factual identifiers, source links, dates and hashes.", "included": "Existing public VAREXIS review records and their limitations; an attributed comparison using the same documented findings.", "excluded": "Upstream documentation bodies, source code, screenshots, logos, private operator templates and protected evidence.", "redistribution_boundary": "Source links and hashes identify upstream material; they do not grant rights to redistribute that material. This package includes no upstream document bodies or code. Existing VAREXIS service terms apply to the supplied compilation.", "terms_url": "https://varexis.tech/checkout-terms", "independent_testing": false }, "delivery_unit": { "kind": "one_published_route", "member_count": 3, "developer_query_units": 1, "research_query_units": 1, "extra_member_purchases": false, "automatic_refresh": false } }, "snapshot_sha256": "c7c7d6732af629186ed5444fa13515a480d7b0c472d6ef4474f24d814acc1949" }