{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:10:55.266Z",
  "record_id": "VXI-EXT-PROCUREMENT-COMPENSATION-RESIDUAL-EFFECTS-01-v1",
  "record_kind": "external_reference",
  "title": "Compensation: Recovery progress and residual effects",
  "system": "Azure Architecture Center",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does completing a compensating workflow prove every original effect was reversed?",
  "near_questions": [
    "Did compensation restore the starting state?",
    "Which effects cannot be undone?",
    "Can compensation itself fail?",
    "Where should failed compensation resume?",
    "Were concurrent changes preserved?",
    "Which undo steps may repeat?",
    "Are residual effects still open?",
    "Who owns manual recovery?",
    "Does cancellation imply compensation completed?",
    "Is this guidance an Azure service guarantee?",
    "What proves each undo action worked?",
    "Can Audit Coverage verify actual compensation?"
  ],
  "supported_claims": [
    {
      "claim": "Microsoft architecture guidance describes compensation as application-specific recovery that must account for concurrent changes. It need not restore the starting state, can itself fail, and needs resumable progress and repeat-safe steps. Irreversible actions require explicit treatment. This is design guidance, not a guarantee for any Azure service or deployed workflow.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A universal undo mechanism, tested compensation implementation or automatic restoration of permissions",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "Microsoft architecture guidance describes compensation as application-specific recovery that must account for concurrent changes. It need not restore the starting state, can itself fail, and needs resumable progress and repeat-safe steps. Irreversible actions require explicit treatment. This is design guidance, not a guarantee for any Azure service or deployed workflow.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Azure Architecture Center: Compensating Transaction pattern",
    "source_url": "https://learn.microsoft.com/en-us/azure/architecture/patterns/compensating-transaction",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-COMPENSATION-RESIDUAL-EFFECTS-01-v1",
    "candidate_record_sha256": "9686caf0e406be5266a6a247b42b168585f3c88572d181cbcb570442b9eff039",
    "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 architecture guidance describes compensation as application-specific recovery that must account for concurrent changes. It need not restore the starting state, can itself fail, and needs resumable progress and repeat-safe steps. Irreversible actions require explicit treatment. This is design guidance, not a guarantee for any Azure service or deployed workflow.",
    "required_buyer_context": "Original effects and operation-specific undo contracts. Compensation attempts, failures and concurrent changes. Residual or irreversible effects, responsible owner and closure 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",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does completing a compensating workflow prove every original effect was reversed?",
    "documented_statement": {
      "status": "documented",
      "statement": "Microsoft architecture guidance describes compensation as application-specific recovery that must account for concurrent changes. It need not restore the starting state, can itself fail, and needs resumable progress and repeat-safe steps. Irreversible actions require explicit treatment. This is design guidance, not a guarantee for any Azure service or deployed workflow.",
      "source_ids": [
        "compensation"
      ]
    },
    "buyer_evidence_required": [
      "Original effects and operation-specific undo contracts.",
      "Compensation attempts, failures and concurrent changes.",
      "Residual or irreversible effects, responsible owner and closure evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline full-restoration claims without per-effect reconciliation; keep failed or irreversible steps explicitly unresolved."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "compensation",
        "url": "https://learn.microsoft.com/en-us/azure/architecture/patterns/compensating-transaction",
        "final_url": "https://learn.microsoft.com/en-us/azure/architecture/patterns/compensating-transaction",
        "title": "Azure Architecture Center: Compensating Transaction pattern",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:10:54.198Z",
        "version_context": "Architecture guidance, not a service-level or implementation guarantee",
        "sha256": "e5717339d02690b1fc1f45e9194e25f11d94ba48bd6dee87607e5b59245b088a",
        "bytes": 65309,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Solution; Problems and considerations"
        ]
      }
    ],
    "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": "An operator needs to know which effects remain before closing a failed multi-service action.",
      "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": "Original effects and operation-specific undo contracts. Compensation attempts, failures and concurrent changes. Residual or irreversible effects, responsible owner and closure evidence."
    },
    "buyer_relevance": "An operator needs to know which effects remain before closing a failed multi-service action.",
    "refusal_conditions": [
      "Decline full-restoration claims without per-effect reconciliation; keep failed or irreversible steps explicitly unresolved."
    ]
  },
  "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#compensating-transaction-residual-effects-recovery",
  "machine_readable_record": "/varexis-index/records/compensating-transaction-residual-effects-recovery.json"
}
