From 8dcb38f7c6deaf445f6a9baaf45e9eec5540fa02 Mon Sep 17 00:00:00 2001
From: stxkxs <139715017+stxkxs@users.noreply.github.com>
Date: Sat, 8 Aug 2026 12:59:18 -0700
Subject: [PATCH] docs: the last copy of the no-backfill claim
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

check-athena-panel-columns.py's scope note described cost-allocation tag
activation as "a live, non-retroactive setting". The live half is right and is
the reason the note exists — this repo cannot know which tag keys the payer
account has activated, so a map key like `user_PlatformId` is unverifiable from
source and the gate says so.

The non-retroactive half is not. AWS backfills up to twelve months, which the
cost-pipeline docs in eks-agent-platform now state correctly; this was the last
copy of the old claim anywhere in the org. What is genuinely unrecoverable is a
resource that ran untagged, because backfill applies an activation status across
history and invents no tag values.

Comment only. The check's behaviour, scope and exit conditions are unchanged.
---
 scripts/check-athena-panel-columns.py | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/scripts/check-athena-panel-columns.py b/scripts/check-athena-panel-columns.py
index 3c8f558..f10b1d7 100755
--- a/scripts/check-athena-panel-columns.py
+++ b/scripts/check-athena-panel-columns.py
@@ -39,8 +39,10 @@
 check MAP KEYS. `element_at(resource_tags, 'user_PlatformId')` is verified as far
 as `resource_tags` being a delivered column; whether `user_PlatformId` is a tag
 the export carries is not knowable from this repo, because it depends on which
-cost-allocation tags are activated in the payer account — a live, non-retroactive
-setting. The `tags`-vs-`resource_tags` half of eks-agent-platform#180 is caught
+cost-allocation tags are activated in the payer account — a live setting this
+repo cannot see. (Activating late is repairable: AWS backfills up to twelve
+months. A resource that ran untagged is not, because backfill applies an
+activation status and invents no tag values.) The `tags`-vs-`resource_tags` half of eks-agent-platform#180 is caught
 here; the `'resourceTags/PlatformId'`-vs-`'user_PlatformId'` half is not, and
 that is the half that fails silently. Asserting it needs a live read.