From 06e7ae0ea53796ba258d3a99b41013708037e39c Mon Sep 17 00:00:00 2001 From: Inferencebot Date: Fri, 13 Nov 2026 20:35:42 +0000 Subject: [PATCH] README: the unmapped-backer step and the notice policy --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index 47040e7..391ea73 100644 --- a/README.md +++ b/README.md @@ -233,6 +233,26 @@ Four jobs run inside the container via `CloudronManifest.json` → `addons.sched investigated, whole hours were missing from it.) Log-scraping jobs cannot be the primary alert for a signal whose window they cannot see. + **Unmapped-backer check** — a contributor who pays but has no portal row never + gets an account, because `fetch_members()` drops every member node with no + email and an OC Organization never exposes one (the mmoya case, found weeks late + by the member asking). `reconcile_unmapped_backers()` reads the RAW member nodes + — including the ones the sweep must skip — and compares them with `members.db`, + reporting three classes because each needs a different action: an ORG account + (link it with `/admin/org-link`), a VISIBLE email (the sweep should have + provisioned it — check the token), and a HIDDEN email (fetch it out-of-band, + then `/admin/provision`). A node with no account object is attributed through + same-day current orders, and is never reported without a date to attribute it + against. On demand: `POST /admin/unmapped-check`. + + **Notice policy (all of the above):** email `info@` only when there is a + problem, and only about what is NEW. What a human has been told is a growing SET + of keys in `portal_state` (`order:grant` / `order:hold`, `slug:class`) — a set + that shrinks (a purchase granted, a finding fixed) mails nobody again, a failed + send retries on the next sweep instead of going quiet, a `notify=False` run is a + look and never consumes the alert, and a clean pass clears the marker so a + recurrence is news again. + **Service-invite triggers:** the sweep is the backstop, not the primary path. Two faster triggers exist, because a member who has just set up their account should not wait hours for forum + Space access: