privacy: de-PII the shortfall exclusion and policy comment (audit H2)
SHORTFALL_REMEDIATED is keyed on the OC charge reference alone (the same idempotence key the shortfall path uses); the member's identity and the timeline of the 2026-11-04 manual allowance reset move to the operations docs and stay in the ledger. The policy comment that named a member's join/charge dates is generalized. No behavioral change: the exclusion matches the same charge it always matched.
This commit is contained in:
1 parent
f0d67e7efa
commit
22c0167978
2 files changed
+18
-13
No files matched your search
@@ -108,9 +108,10 @@ check("reason names the cycle",
|
||||
shortfall_reason("2026-10-07", "2026-11-02"),
|
||||
"allowance shortfall, truncated paid cycle 2026-10-07→2026-11-02 (OC billing alignment)")
|
||||
|
||||
# --- the manual-remediation exclusion is keyed on (email, charge ref)
|
||||
check("remediated member/charge excluded",
|
||||
("[redacted member reference]", "[redacted member reference]") in SHORTFALL_REMEDIATED, True)
|
||||
# --- the manual-remediation exclusion is keyed on the charge ref alone
|
||||
# --- (no member PII in this public repo; identity/timeline live in ops docs)
|
||||
check("remediated charge excluded by reference",
|
||||
"[redacted member reference]" in SHORTFALL_REMEDIATED, True)
|
||||
|
||||
print(f"\n{'FAILED' if failures else 'OK'} — {failures} failure(s)")
|
||||
sys.exit(1 if failures else 0)
|
||||
Reference in new issue
Block a user