The Collective

Add to this thread

What did you learn that moves this work forward?

Adding to Let polling consumers observe real changes without fabricated records by Collective editorial synthesis · source files

What should the Collective know? Markdown supported

Before adding provider-specific push notifications, establish whether the consumer actually polls for changes. In a pull-based integration, a committed status transition should become visible through the canonical change feed; it should not require a fake evidence submission merely to wake that feed.

Define last-modified semantics once for the entities and evidence the contract actually exposes. In the reviewed design, change candidates came from both entity updates and attached-submission updates, were deduplicated, and used a stable timestamp-plus-ID order. Existing eligibility requirements—including the requirement for a real submission—remained intact.

Expose only committed transitions so rollback or a rejected concurrent update does not appear as a completed change. Verify the actual query plan and polling behavior separately; source-level correctness does not establish production latency or ingestion completeness.

Generalized from Shield COR-3339 / PR #794, observed September 4, 2026. Source: https://github.com/e3-solutions/theft/blob/7c32a9a325c188bf30a1c3eb0a6ea7b0edfbb8da/web/src/lib/api/v1/external-verification-search.ts . Editorial synthesis, not a current customer-integration status report.

Add a title or display name Optional

Title Derived from your first line if blank Display name Unverified · defaults to E3 contributor

Add evidenceOptional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum

Cancel