{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:18:09.489Z",
  "record_id": "VXI-EXT-PROCUREMENT-FOCUS-LEDGER-CORRECTION-REVERSAL-PAIRING-01-v1",
  "record_kind": "external_reference",
  "title": "FOCUS ledger correction reconstruction",
  "system": "FinOps FOCUS 1.4",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "How should I distinguish a FOCUS Ledger reversal from a second charge?",
  "near_questions": [
    "What identifies a FOCUS ledger reversal?",
    "Are opposite-sign rows duplicate transactions?",
    "Does a negative FOCUS correction prove a refund?",
    "How are original and corrected entries reconciled?"
  ],
  "supported_claims": [
    {
      "claim": "FOCUS 1.4 Ledger corrections append explicit reversals and re-entries as applicable: a reversal changes additive metric signs while other columns match the original, and a corrected record can follow. All artifacts remain relevant to the scope aggregate. Negative and positive rows need their correction context; their presence alone does not establish duplicate billing or a cash refund.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Financial transfers and the complete buyer ledger are unverified.",
    "FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "FOCUS 1.4 Ledger corrections append explicit reversals and re-entries as applicable: a reversal changes additive metric signs while other columns match the original, and a corrected record can follow. All artifacts remain relevant to the scope aggregate. Negative and positive rows need their correction context; their presence alone does not establish duplicate billing or a cash refund.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "FOCUS 1.4 — Correction Handling",
    "source_url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/attributes/correction_handling.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-FOCUS-LEDGER-CORRECTION-REVERSAL-PAIRING-01-v1",
    "candidate_record_sha256": "3b0fd080f6f5377c7fead5b06efe882581531d0cc6a93204608da648a23966a5",
    "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": "FOCUS 1.4 Ledger corrections append explicit reversals and re-entries as applicable: a reversal changes additive metric signs while other columns match the original, and a corrected record can follow. All artifacts remain relevant to the scope aggregate. Negative and positive rows need their correction context; their presence alone does not establish duplicate billing or a cash refund.",
    "required_buyer_context": "Original, reversal and corrected entries; Additive metrics and matching dimensions; Delivery scope, order and correction 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",
    "checked_on": "2026-10-24",
    "claim_to_check": "How should I distinguish a FOCUS Ledger reversal from a second charge?",
    "documented_statement": {
      "status": "documented",
      "statement": "FOCUS 1.4 Ledger corrections append explicit reversals and re-entries as applicable: a reversal changes additive metric signs while other columns match the original, and a corrected record can follow. All artifacts remain relevant to the scope aggregate. Negative and positive rows need their correction context; their presence alone does not establish duplicate billing or a cash refund.",
      "source_ids": [
        "focus-correction_handling"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconstruct corrected charges without confusing reversals with new transactions. This is a proposed evidence review, not an observed billing reconciliation.",
      "source_ids": [
        "focus-correction_handling"
      ]
    },
    "buyer_evidence_required": [
      "Original, reversal and corrected entries",
      "Additive metrics and matching dimensions",
      "Delivery scope, order and correction policy"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer duplicate billing or refunded cash from a ledger sign pattern alone."
    },
    "unknowns": "Financial transfers and the complete buyer ledger are unverified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Financial transfers and the complete buyer ledger are unverified."
    },
    "evidence_sources": [
      {
        "source_id": "focus-correction_handling",
        "url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/attributes/correction_handling.md",
        "final_url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/attributes/correction_handling.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:03:39.987Z",
        "sha256": "24ce83c40e29b60a11e905f5ec929f934b189b1373addb19474a41ee30ce0716",
        "bytes": 8650,
        "title": "FOCUS 1.4 — Correction Handling",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original bounded paraphrase of FOCUS 1.4 by Joint Development Foundation Projects LLC, FOCUS Series and contributors; CC-BY-4.0 (https://creativecommons.org/licenses/by/4.0/). This review changes the wording and adds explicitly labelled review judgments. Pinned source attribution is supplied; source bodies remain private and are not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Overview and normative requirements of the cited FOCUS 1.4 columns or attributes"
        ],
        "version_context": "FOCUS 1.4; released 2026-06-04; pinned FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec revision f1eeb30a78f7c141ef1237d589355296a2761c1c. Requirements are documentation evidence, not verified supplier conformance."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Reconstruct corrected charges without confusing reversals with new transactions.",
      "free": "Complete review, sources, practical questions 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 the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome."
    },
    "buyer_relevance": "Reconstruct corrected charges without confusing reversals with new transactions.",
    "refusal_conditions": [
      "Do not infer duplicate billing or refunded cash from a ledger sign pattern alone."
    ]
  },
  "niche": {
    "niche_id": "ai-infrastructure-cost-evidence",
    "label": "AI Infrastructure, Metering & FinOps Evidence",
    "classification_id": "finops",
    "classification_label": "AI Infrastructure, Metering & FinOps Verification",
    "topic_id": "finops",
    "buyer_intent": "Reconstruct corrected charges without confusing reversals with new transactions.",
    "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#focus-ledger-correction-reversal-pairing",
  "machine_readable_record": "/varexis-index/records/focus-ledger-correction-reversal-pairing.json"
}