Featurebase source: https://cardeio.featurebase.app/p/summonersbase-link Submitted: 2026-07-01 by Joe W Upvotes: 1 Category: Player Networks
Problem / request: SummonersBase developer saw the Piltover Archive account-linking/deck-sync work and wants SummonersBase supported as a Riftbound deck builder integration.
Why this is not ready for implementation: This is a partnership/product decision before it is an engineering task. We need to decide whether to support another external deck-sync partner and what minimum partner contract/security requirements apply.
Duplicate / adjacent sweep:
- No exact SummonersBase ticket found.
- Adjacent Piltover work exists (, , , ) but is partner-specific.
- Adjacent generic import items include old/canceled import-export tickets and , but none own this Riftbound/SummonersBase partner request.
Open product questions:
- Do we want to accept SummonersBase as an integration partner for Riftbound?
- Should future deck-sync partners use a generic partner API/contract or remain bespoke?
- What requirements must a partner meet: auth/signing, deck schema compatibility, support owner, launch comms, and data/privacy review?
90/10 if approved: Create a partner-onboarding checklist and technical discovery ticket, reusing Piltover's HMAC/auth and import flow where possible.
Done for scoping:
- Product chooses accept, decline, or park.
- If accepted, partner requirements and product owner are defined.
- Engineering follow-up has testable acceptance criteria for connection, import/sync behavior, error handling, and partner authentication.
Automated triage by ProductClaw.
