What is being tested
Did deleted container artifacts remain billable because shared layers were still retained? The boundary for this investigation is artifact registry deleted-layer retention charges. Begin with the disputed transaction or population, then identify which artifact deletion log establishes the observed position and which layer reference manifest supports the comparison. A difference in totals should not replace this question.
Evidence: artifact deletion log
For artifact registry deleted-layer retention charges, artifact deletion log must be linked to layer reference manifest. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.
Evidence: layer reference manifest
For artifact registry deleted-layer retention charges, layer reference manifest must be linked to retention policy. Retain stable identifiers and their effective relationships. Current labels are insufficient when assets or accounts changed during the period. Explain one-to-many relationships explicitly and preserve the history needed to distinguish an alias, replacement or reassignment from a genuinely additional item.
Evidence: retention policy
For artifact registry deleted-layer retention charges, retention policy must be linked to registry storage invoice. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.
Evidence: registry storage invoice
For artifact registry deleted-layer retention charges, registry storage invoice must be linked to artifact deletion log. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.
Reconciliation logic
Compare logical artifact deletion with actual referenced layer retention before recomputing the stored-byte population. Build the comparison at the level identified by artifact deletion log and retain the governing version from layer reference manifest. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A shared layer can remain required by another image. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked artifact deletion log, layer reference manifest, retention policy, registry storage invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.
Human review and outcome
Release engineering validates references and cleanup policy. Retain a layer-level retention explanation or supported post-purge query. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.
Limitations and processing boundary
Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of artifact deletion log or layer reference manifest limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.
AuditRes pathway
Discuss artifact registry deleted-layer retention charges in the Technology Spend workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.
AuditRes Technology Spend: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.
Neighboring financial questions
- Review observability ingestion and retention billing
- Collaboration recording storage retention surcharge
- AI cached-input price classification
- AI embedding refresh versus incremental indexing costs
Technology Spend resource hub · All guides in this evidence collection