{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T17:54:06.066Z",
  "record_id": "VXI-EXT-PROCUREMENT-GRAPH-BATCH-PER-REQUEST-01-v1",
  "record_kind": "external_reference",
  "title": "Microsoft Graph: Batch success and individual failures",
  "system": "Microsoft Graph",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does HTTP 200 for a Microsoft Graph batch prove every agent action in it succeeded?",
  "near_questions": [
    "Can a Graph batch return 200 with failed requests?",
    "Which individual Graph requests were throttled?",
    "What does status 424 mean in this batch?",
    "Which request IDs match the failed responses?",
    "Did a dependency fail before the next action?",
    "Is the batch response being treated as one transaction?",
    "Were successful operations excluded from a blind replay?",
    "What evidence shows each directory change completed?",
    "Which Graph API version did each request target?",
    "Can Audit Coverage verify actual Graph batch outcomes?",
    "What response headers inform recovery?",
    "Does one successful request prove the whole agent task finished?"
  ],
  "supported_claims": [
    {
      "claim": "A parseable Graph batch can return HTTP 200 while individual responses fail. Each response has its own identifier and status; throttling applies per request, and requests depending on a failed request receive 424. Recovery must use those individual results rather than the outer status alone.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Atomic batch execution, automatic rollback or safe replay of already completed operations",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "A parseable Graph batch can return HTTP 200 while individual responses fail. Each response has its own identifier and status; throttling applies per request, and requests depending on a failed request receive 424. Recovery must use those individual results rather than the outer status alone.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Microsoft Graph: Combine multiple HTTP requests using JSON batching",
    "source_url": "https://learn.microsoft.com/en-us/graph/json-batching",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GRAPH-BATCH-PER-REQUEST-01-v1",
    "candidate_record_sha256": "7f000ed01270d6f75ae93ac70deeac941719da1249bdf4225bfaf601b1024432",
    "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": "A parseable Graph batch can return HTTP 200 while individual responses fail. Each response has its own identifier and status; throttling applies per request, and requests depending on a failed request receive 424. Recovery must use those individual results rather than the outer status alone.",
    "required_buyer_context": "Batch request identifiers, target API versions and dependsOn relationships. Every individual response status, headers and business result. A justified retry or reconciliation plan for each failed or uncertain operation. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does HTTP 200 for a Microsoft Graph batch prove every agent action in it succeeded?",
    "documented_statement": {
      "status": "documented",
      "statement": "A parseable Graph batch can return HTTP 200 while individual responses fail. Each response has its own identifier and status; throttling applies per request, and requests depending on a failed request receive 424. Recovery must use those individual results rather than the outer status alone.",
      "source_ids": [
        "graph-batch"
      ]
    },
    "buyer_evidence_required": [
      "Batch request identifiers, target API versions and dependsOn relationships.",
      "Every individual response status, headers and business result.",
      "A justified retry or reconciliation plan for each failed or uncertain operation."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline all-actions-complete claims based on the batch HTTP code; inspect each result and dependency before selecting recovery actions."
    },
    "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": "graph-batch",
        "url": "https://learn.microsoft.com/en-us/graph/json-batching",
        "final_url": "https://learn.microsoft.com/en-us/graph/json-batching",
        "title": "Microsoft Graph: Combine multiple HTTP requests using JSON batching",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T17:50:56.360Z",
        "version_context": "Rolling JSON batching documentation",
        "sha256": "0be35f4e6828b86d8c0dda8c7d20d1eff1ece1cd8e2646bc74fbf401b9cb3ce6",
        "bytes": 63167,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Processing the JSON batch response; Sequencing requests; Batch size limitations"
        ]
      }
    ],
    "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": "Multi-step directory or content automation needs to separate completed operations, rejected requests and failed dependencies before deciding what to repeat.",
      "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": "Batch request identifiers, target API versions and dependsOn relationships. Every individual response status, headers and business result. A justified retry or reconciliation plan for each failed or uncertain operation."
    },
    "buyer_relevance": "Multi-step directory or content automation needs to separate completed operations, rejected requests and failed dependencies before deciding what to repeat.",
    "refusal_conditions": [
      "Decline all-actions-complete claims based on the batch HTTP code; inspect each result and dependency before selecting recovery actions."
    ]
  },
  "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#graph-json-batch-status-per-request-recovery",
  "machine_readable_record": "/varexis-index/records/graph-json-batch-status-per-request-recovery.json"
}
