Live projection evidence¶

On 2026-09-17, ShouldaUsedThat compiled this repository's public profile, read the authenticated pradeeptathineni GitHub account, sealed an additive plan, applied it interactively, and then performed an independent full readback. It later refreshed its own release evidence, resealed the catalog, proved the resulting projection was a semantic no-op, and independently read everything back again.

Verified result¶

• 221 reviewed catalog records from 2 exact public sources
• 218 projectable repositories; 2 rejects and 1 watch entry remained catalog-only
• 12 public GitHub Lists
• 248 intentional repository-to-List memberships
• 438 initial sealed additive operations: 10 List creates, 186 stars, and 242 memberships
• 488 / 488 initial independent postconditions verified with 0 mismatches
• 0 operations in the current metadata-only follow-up plan; the existing projection was exact
• 730 / 730 current independent postconditions verified with 0 mismatches
• 275 total public stars after projection, including unrelated pre-existing stars that the product deliberately leaves alone

The initial verification comprised 218 stars, 248 intended memberships, 7 preserved pre-existing memberships, 12 exact public List definitions, and one condition each for account identity, capability, and additive state integrity. The current replay rechecked the same desired state and all 249 observed memberships as preserved additive state, producing 730 verified conditions. The canonical public curation fingerprint is curation_71798ffe0de72ea641ceea71746c7084c3bb0ecb1adb25e7c9e2e2d5cab73310.

Public Lists¶

The one public-count difference is evidence of the additive boundary, not catalog drift: an existing membership that was outside the new intended set remained untouched. No List is private, and every List fit in one complete readback page at verification time.

The repository proves its own intent¶

pradeeptathineni/shoulda-used-that is itself reviewed in the catalog and publicly appears in OSS Curation & Prior Art and Platform Engineering & Delivery. The same installed distribution produced the evidence corpus and, through the shoulda catalog and shoulda github command groups, the live projection, apply receipts, independent verification, and public export that underpin this page.

Evidence boundary¶

This page publishes aggregate, independently rechecked outcomes. The private external state keeps the exact account node ID, capability payload, sealed plan, operation receipts, mutation IDs, and raw API responses. A GitHub star remains a consideration bookmark; the catalog's role, rationale, disposition, freshness, and reconsideration trigger remain the stronger evidence.