“Worker V5.8.4 adds an optional LISTED_UPLS variable that filters which listed registry records appear in the public index and sitemap, while leaving all records fully accessible via direct lookup, admin view, snapshots and backups.”
PropositionsT1: Optional env variable LISTED_UPLS accepts registry codes separated by commas, spaces, semicolons or newlines | T2: listedSelection() parses and uppercases LISTED_UPLS into a Set of valid UPL codes, returning null if empty or absent | T3: isShown() returns true only for records that are listed and whose code is in the active selection (or all listed records when no selection is active) | T4: Public /registry/index.json and sitemap filter output through isShown(); admin view (?k=ADMIN_TOKEN) bypasses the filter and returns every record | T5: Response envelope adds not_shown_count (listed records outside selection) and selection_active flag; existing fields count, not_listed_count and total_count retain V5.8.3 semantics | T6: All records remain in _index, anchor snapshots, backup, /registry/{UPL}.json, landing pages and /registry/lookup regardless of selection state | T7: Unlisted visibility (V5.7) is unchanged and is the correct mechanism for records that must not expose their title
ConstraintsRequires base Worker V5.8.3 CORE_FIT (UPL-TECH-26-884614-EN); LISTED_UPLS must contain codes matching UPL_RE pattern; feature is inert when LISTED_UPLS is empty or absent; this is a presentation filter only, not an access-control or privacy mechanism; unlisted visibility remains the sole privacy tool
MechanismsT1: Set LISTED_UPLS to a mixed-delimiter string and confirm all valid codes are parsed; test empty and absent values confirm no behaviour change | T2: Unit-test listedSelection() with valid codes, invalid codes, mixed delimiters, empty string and null env; verify Set contents and null return | T3: Unit-test isShown() for listed-in-selection, listed-outside-selection, unlisted and null-entry inputs | T4: Fetch public index and confirm only selection codes appear; fetch with ?k=ADMIN_TOKEN and confirm all 55 records returned | T5: Validate envelope fields: count=15, not_listed_count=1, not_shown_count=39, total_count=55, selection_active=true against live deployment of 5 Oct 2026 | T6: Fetch /registry/lookup for UPL-TECH-26-100161-EN (outside selection) and confirm full record returned; verify record present in backup and snapshots | T7: Confirm an unlisted record is absent from public index independent of LISTED_UPLS state
BoundariesNo changes to certificate issuance, landing pages, lookup endpoint, anchor snapshots, backup tooling or unlisted visibility logic; access control and privacy features are out of scope for this version; no UI for managing LISTED_UPLS is built. OPEN: behaviour when LISTED_UPLS contains codes for unlisted records is not explicitly defined; no documented limit on the number of codes LISTED_UPLS may contain; no stated behaviour if UPL_RE is undefined or misconfigured.