{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:18:09.489Z",
  "record_id": "VXI-EXT-PROCUREMENT-FOCUS-SPLIT-ALLOCATION-CONSERVATION-01-v1",
  "record_kind": "external_reference",
  "title": "FOCUS split charge conservation",
  "system": "FinOps FOCUS 1.4",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "What must remain consistent when a FOCUS origin charge is split across teams?",
  "near_questions": [
    "Should split FOCUS costs sum back to their origin?",
    "Can allocation change an original unit price?",
    "How do I detect cost created by splitting a row?",
    "Does allocation arithmetic establish fair chargeback?"
  ],
  "supported_claims": [
    {
      "claim": "FOCUS 1.4 requires summable costs and quantities across allocated charges to reproduce the origin charge, while dimensions and non-summable metrics such as unit prices retain origin values when present. A split redistributes a charge rather than creating cost. Arithmetic conservation supports consistency review but does not establish fair allocation or correct metering.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Underlying metering and allocation fairness remain 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 requires summable costs and quantities across allocated charges to reproduce the origin charge, while dimensions and non-summable metrics such as unit prices retain origin values when present. A split redistributes a charge rather than creating cost. Arithmetic conservation supports consistency review but does not establish fair allocation or correct metering.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "FOCUS 1.4 — Data Generator-Calculated Split Cost Allocation Handling",
    "source_url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/attributes/data_generator_calculated_split_cost_allocation_handling.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-FOCUS-SPLIT-ALLOCATION-CONSERVATION-01-v1",
    "candidate_record_sha256": "416b0476f330bc716c66475e66e35103053d7b3e198121316d87819ba1c55d13",
    "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 requires summable costs and quantities across allocated charges to reproduce the origin charge, while dimensions and non-summable metrics such as unit prices retain origin values when present. A split redistributes a charge rather than creating cost. Arithmetic conservation supports consistency review but does not establish fair allocation or correct metering.",
    "required_buyer_context": "Origin charge and all allocated children; Summable and non-summable column definitions; Allocation method and recipient mapping. 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": "What must remain consistent when a FOCUS origin charge is split across teams?",
    "documented_statement": {
      "status": "documented",
      "statement": "FOCUS 1.4 requires summable costs and quantities across allocated charges to reproduce the origin charge, while dimensions and non-summable metrics such as unit prices retain origin values when present. A split redistributes a charge rather than creating cost. Arithmetic conservation supports consistency review but does not establish fair allocation or correct metering.",
      "source_ids": [
        "focus-data_generator_calculated_split_cost_allocation_handling"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check whether a cost-allocation transformation conserves the original charge. This is a proposed evidence review, not an observed billing reconciliation.",
      "source_ids": [
        "focus-data_generator_calculated_split_cost_allocation_handling"
      ]
    },
    "buyer_evidence_required": [
      "Origin charge and all allocated children",
      "Summable and non-summable column definitions",
      "Allocation method and recipient mapping"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not accept an allocation that creates or loses cost without an explained adjustment."
    },
    "unknowns": "Underlying metering and allocation fairness remain unverified.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Underlying metering and allocation fairness remain unverified."
    },
    "evidence_sources": [
      {
        "source_id": "focus-data_generator_calculated_split_cost_allocation_handling",
        "url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/attributes/data_generator_calculated_split_cost_allocation_handling.md",
        "final_url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/attributes/data_generator_calculated_split_cost_allocation_handling.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:03:40.921Z",
        "sha256": "ac2be6b0a233dee46b67dc254c9ce25b20a17b1445522b4ab7477bb9eb56e2a8",
        "bytes": 2034,
        "title": "FOCUS 1.4 — Data Generator-Calculated Split Cost Allocation 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": "Check whether a cost-allocation transformation conserves the original charge.",
      "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": "Check whether a cost-allocation transformation conserves the original charge.",
    "refusal_conditions": [
      "Do not accept an allocation that creates or loses cost without an explained adjustment."
    ]
  },
  "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": "Check whether a cost-allocation transformation conserves the original charge.",
    "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-split-allocation-conservation",
  "machine_readable_record": "/varexis-index/records/focus-split-allocation-conservation.json"
}