{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T22:18:09.489Z",
  "record_id": "VXI-EXT-PROCUREMENT-FOCUS-ALLOCATED-TAGS-ATTRIBUTION-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "FOCUS origin tags versus allocated tags",
  "system": "FinOps FOCUS 1.4",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can origin resource tags alone identify the team charged by a FOCUS cost split?",
  "near_questions": [
    "Are FOCUS AllocatedTags the same as resource tags?",
    "Can a split charge have no allocated tags?",
    "Which tags identify a shared-service cost recipient?",
    "Do original tags prove acceptance of an allocated charge?"
  ],
  "supported_claims": [
    {
      "claim": "FOCUS 1.4 separates AllocatedTags for allocated charges from resource tags already present in Tags. AllocatedTags must not repeat those resource tags and may be null even for a split charge. The originating resource owner and allocated recipient need not be interchangeable; absence of allocation tags does not prove the origin owner accepted that share.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Buyer ownership and approval mappings are unknown.",
    "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 separates AllocatedTags for allocated charges from resource tags already present in Tags. AllocatedTags must not repeat those resource tags and may be null even for a split charge. The originating resource owner and allocated recipient need not be interchangeable; absence of allocation tags does not prove the origin owner accepted that share.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "FOCUS 1.4 — Allocated Tags",
    "source_url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/datasets/cost_and_usage/columns/allocatedtags.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-FOCUS-ALLOCATED-TAGS-ATTRIBUTION-BOUNDARY-01-v1",
    "candidate_record_sha256": "84789f8b8b0f9417bc78aa85532b57caf5f0e242a3aabadc32b9dc7d695b3e93",
    "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 separates AllocatedTags for allocated charges from resource tags already present in Tags. AllocatedTags must not repeat those resource tags and may be null even for a split charge. The originating resource owner and allocated recipient need not be interchangeable; absence of allocation tags does not prove the origin owner accepted that share.",
    "required_buyer_context": "Origin resource tags; Allocated resource identity and allocated tags; Approved recipient mapping and allocation method. 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": "Can origin resource tags alone identify the team charged by a FOCUS cost split?",
    "documented_statement": {
      "status": "documented",
      "statement": "FOCUS 1.4 separates AllocatedTags for allocated charges from resource tags already present in Tags. AllocatedTags must not repeat those resource tags and may be null even for a split charge. The originating resource owner and allocated recipient need not be interchangeable; absence of allocation tags does not prove the origin owner accepted that share.",
      "source_ids": [
        "focus-cu-allocatedtags"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Avoid assigning shared-service costs to the wrong organisational owner. This is a proposed evidence review, not an observed billing reconciliation.",
      "source_ids": [
        "focus-cu-allocatedtags"
      ]
    },
    "buyer_evidence_required": [
      "Origin resource tags",
      "Allocated resource identity and allocated tags",
      "Approved recipient mapping and allocation method"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer a recipient or business approval solely from original resource tags."
    },
    "unknowns": "Buyer ownership and approval mappings are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Buyer ownership and approval mappings are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "focus-cu-allocatedtags",
        "url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/datasets/cost_and_usage/columns/allocatedtags.md",
        "final_url": "https://raw.githubusercontent.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/f1eeb30a78f7c141ef1237d589355296a2761c1c/specification/datasets/cost_and_usage/columns/allocatedtags.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T22:03:38.008Z",
        "sha256": "7841dc2c97f0e1f270351774dfca6bd6943e9df39b0e9157181959d82ab43cdf",
        "bytes": 3618,
        "title": "FOCUS 1.4 — Allocated Tags",
        "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": "Avoid assigning shared-service costs to the wrong organisational owner.",
      "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": "Avoid assigning shared-service costs to the wrong organisational owner.",
    "refusal_conditions": [
      "Do not infer a recipient or business approval solely from original resource tags."
    ]
  },
  "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": "Avoid assigning shared-service costs to the wrong organisational owner.",
    "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-allocated-tags-attribution-boundary",
  "machine_readable_record": "/varexis-index/records/focus-allocated-tags-attribution-boundary.json"
}