{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-11T17:52:53.561Z",
  "record_id": "VXI-BDAS-20261011-WORKLOAD-COMPARABILITY-REVIEW-v1",
  "record_kind": "supplied_review_summary",
  "title": "Benchmark review: Keep different workload claims separate",
  "system": "BDAS",
  "evidence_family": "supplied_workload_comparability_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "REPORTED_WORKLOAD_BOUNDARIES_NO_NEW_BENCHMARK",
  "canonical_question": "Can a benchmark gain on repeated work support a claim about processing new inputs?",
  "near_questions": [
    "Can repeated-work benchmarks prove new-input speed?",
    "When are performance results comparable?",
    "Can a result be reused for a different workload claim?",
    "Does a lineage review produce new benchmark evidence?",
    "What must match before comparing acceleration results?",
    "Do different output requirements change a benchmark claim?",
    "Does reviewing old results create fresh validation?",
    "Can a historical benchmark establish customer savings?",
    "Should workload assumptions accompany a speed claim?",
    "Can a product change inherit an earlier performance result?",
    "Does a new review date make a benchmark newly measured?",
    "What limits should an agent retain when citing a performance gain?"
  ],
  "supported_claims": [
    {
      "claim": "The supplied lineage review keeps an existing result for repeated-work conditions separate from evaluations of new-input processing. Their recorded gains cannot be transferred between the two claims. The review reports no new runtime measurements and uses historical evaluation material; it does not establish fresh holdout performance or customer savings. Before comparing results, require matching workload assumptions, required outputs and cost accounting.",
      "reliance": "SUPPLIED_REVIEW_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "performance gains transferred between different workloads",
    "new benchmark measurements from a lineage review",
    "fresh holdout validation from historical material",
    "customer savings or production qualification"
  ],
  "public_summary": "The supplied lineage review keeps an existing result for repeated-work conditions separate from evaluations of new-input processing. Their recorded gains cannot be transferred between the two claims. The review reports no new runtime measurements and uses historical evaluation material; it does not establish fresh holdout performance or customer savings. Before comparing results, require matching workload assumptions, required outputs and cost accounting.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "varexis_supplied_review",
    "source_record_id": "bdas-20261011-workload-lineage-review",
    "supplied_review_sha256": "b4b90ca62a3d1702ee122191b03cdee565909b9c589fe2e17a4ff5b3307709f1",
    "supplied_lineage_sha256": "80772564474897311d6552ba841b67a76ca653a6f6408a0a13d8246751403e2a",
    "checked_on": "2026-10-11",
    "underlying_archive_reverified": false,
    "experiments_rerun": false,
    "independent_replication_claimed": false,
    "method": "Supplied review and lineage files read and hashed. Their archive-integrity and experimental claims were not independently reverified during this intake.",
    "source_visibility": "Supplied operator review material; protected details are excluded from public and paid delivery."
  },
  "answer_policy": {
    "classification": "SUPPLIED_REVIEW_WITH_BOUNDARIES",
    "bounded_answer": "The supplied lineage review keeps an existing result for repeated-work conditions separate from evaluations of new-input processing. Their recorded gains cannot be transferred between the two claims. The review reports no new runtime measurements and uses historical evaluation material; it does not establish fresh holdout performance or customer savings. Before comparing results, require matching workload assumptions, required outputs and cost accounting.",
    "required_buyer_context": "Workload assumptions, output requirements, timing and cost boundaries, evaluation-data status and the exact claimed use. Protected mechanisms and measurements remain excluded.",
    "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.",
  "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": "evidence_receipt",
    "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#benchmark-reuse-and-new-input-claims",
  "machine_readable_record": "/varexis-index/records/benchmark-reuse-and-new-input-claims.json"
}
