External raffle providers

CollabOS uses a provider layer so external raffle platforms can feed the same Canonical Project Database and Collab Tracker workflow without replacing native raffles.

Current provider modes

CollabOS Native

• first-party raffle engine
• managed directly in CollabOS

Alphabot

• existing Alphabot integration remains intact
• the provider layer reads it through a compatibility adapter
• Alphabot-specific behavior is not replaced by the generic provider layer

Tessera

• read-only external provider integration
• API credential is backend-only
• raffles are normalized into CollabOS provider records
• project, runner, allocation, requirements, counts, status, dates, and published winners can be synchronized when Tessera exposes them

Scheduled sync cadence

Tessera scheduled backup synchronization follows the same 12-hour cadence as the Alphabot scheduled backup sync. The management page still provides Sync now for an immediate manual refresh.

The scheduled job uses incremental updated-since synchronization with an overlap window and a database lease so multiple CollabOS instances do not intentionally run the same provider sync concurrently.

Runner matching

CollabOS attempts runner matching in this order:

1. 1.saved provider runner mapping
2. 2.stable Discord ID
3. 3.stable X user ID
4. 4.exactly one matching workspace member

Ambiguous runner matches are not guessed. They remain Needs Review until a manager confirms or claims the raffle.

Winner privacy

Provider winners are only user-visible when the provider says the winner list is public. If Tessera later stops exposing the winners publicly, cached user-visible winner identity rows are removed instead of leaving stale public wins.