FablePool Discord Bot — discover, follow & back FablePool projects from any Discord server

Build a first-class, production-ready Discord integration for FablePool so that ANY Discord community can discover, follow, discuss, and back FablePool projects directly from their own server — not just from one official channel. Context — how FablePool works (so this build fits the platform): FablePool crowdfunds ambitious AI builds in public. A maker submits a prompt; an AI planner turns it into a sequence of milestones, each with a funding target priced in credits; backers pledge credits into a project's funding pool; once a milestone is funded the build runs autonomously, and every milestone, build-log entry, released artifact, and credit-ledger movement is public. fablepool.com MUST remain the canonical system of record for identity, credits, billing, invoices, refunds, fraud checks, project state, the public ledger, moderation, and artifacts. Discord is purely the social and command surface. The bot must NEVER touch card details, payment credentials, or billing — all credit purchases, top-ups, receipts, refunds, and ledger writes stay on fablepool.com. Deliver these capabilities: 1) Bot install & authorization. Secure Discord OAuth install flow with least-privilege permissions; configuration at both server (guild) and channel level. A server can connect to one or more FablePool projects; a project can appear in multiple servers, subject to the project owner's permission and anti-spam rules. 2) Project ↔ channel binding. Authorized users bind a Discord channel to a specific FablePool project (e.g. a #fablepool-open-source-bloomberg channel that carries one project's updates). Slash commands: /fablepool connect, bind-project, unbind-project, project, status, milestones, funding, buildlog, follow, back, discover, search, settings, help. 3) Discovery inside Discord. Browse featured, trending, nearly-funded, and recently launched projects, or search by query (e.g. "open source finance"). Responses use rich embeds showing: title, short summary, funding target (credits), credits raised, % funded, current milestone, backer count, artifact license, project status, and a link to the project on fablepool.com — with Follow and Back buttons. 4) Backing with FablePool credits. A linked user can pledge credits to a project's funding pool from any server where the bot is installed and the project is visible (not only an official server). Flow: "/fablepool back project:<id> amount:<credits>" → an ephemeral confirmation embed ("Back <project> with N credits?") with Confirm / Change amount / View project / Cancel. On explicit confirm: if the user has linked their FablePool account and holds enough credits, record the pledge in the SAME credit ledger and project funding pool as a website pledge. If the user is unlinked, return a secure account-linking URL; if short on credits, return a secure fablepool.com top-up link. All pledges must be idempotent (idempotency keys; safe against double-clicks and Discord interaction retries) — never create duplicate pledges. Confirmations link back to the canonical FablePool transaction/receipt and project page, and the public funding total updates correctly. 5) Account linking. Secure Discord↔FablePool linking using short-lived signed URLs, CSRF protection, an explicit consent screen, and revocation. Users can unlink at any time. Handle a FablePool user changing Discord accounts, leaving a server, or joining multiple servers. 6) Notifications into bound channels. Auto-post project lifecycle events: plan generated, submitted for review, approved / rejected / sent back, milestone added or edited, funding target changed, new backing received, funding crossing 25% / 50% / 75% / 100%, milestone started, milestone completed, artifact released, build-log entry posted, project cancelled or archived, and refund/credit events affecting the project. Server admins and project owners choose which events post; support quiet mode, digest mode, and major-updates-only mode to avoid channel spam. 7) Roles & permissions. Role-aware behaviour across server admin, project owner, builder, backer, reviewer, moderator, follower, and general member. Only authorized users may bind/unbind projects, change notification settings, or trigger admin actions. Backers can opt into private updates about projects they've backed. Never expose a user's credit balance or other private information in public channels. 8) Embeds, buttons, menus, modals. Polished project cards and update embeds with clear calls to action: View project, Follow, Back, View milestones, View build log, Share. Use Discord buttons, select menus, and modals for a smooth UX. 9) Admin & moderation. FablePool admins can see which guilds have installed the bot and which projects are bound to which servers/channels; and can disable a server integration, block a guild, disconnect a project from Discord, or bar a project from bot promotion. Moderation hooks for spam, misleading promotion, abuse, and suspicious backing activity; plus abuse reporting. 10) Analytics (privacy-respecting). Track Discord-sourced project views, button clicks, follows, backing attempts, completed backings, active servers/channels, and view→back conversion — without exposing user-level financial data to server admins. 11) Security (production-grade). OAuth install, signed short-lived authorization links, CSRF, permission and role checks, rate limiting, interaction replay protection, idempotency keys for backing, audit logs for admin actions, webhook signature verification where applicable, secure storage of Discord tokens with rotation and revocation, safe error handling, and anti-spam protections. Unauthorized users must never impersonate project owners, manipulate funding, alter project settings, or post fake build-log entries. 12) Documentation: installing the bot, connecting a server, binding a project, configuring notifications, using the slash commands, backing from Discord, linking/unlinking accounts, roles & permissions, the security model, and troubleshooting. Suggested fundable milestones (the planner may refine these): (M1) Read-only notification MVP — bot, OAuth install, basic server authorization, bind one project to one channel, read-only rich-embed updates, and /fablepool project|status|help. (M2) Discovery & polished embeds — discover / search / trending / nearly-funded, the milestones/funding/buildlog commands, and View project / Follow / Share buttons. (M3) Account linking & following — secure linking with consent and revocation, following projects, and private updates. (M4) Backing with credits — /fablepool back with ephemeral confirmation, idempotent pledge handling, insufficient-credit and secure top-up handling, and canonical ledger recording on FablePool. (M5) Multi-server / multi-project — many projects per server, one project promoted across many servers (subject to permissions & anti-spam), channel-level config, notification filtering, digest and role-aware settings. (M6) Moderation, admin controls, analytics & hardening — admin dashboards, audit logs, abuse controls, rate limiting, analytics, retry and failure monitoring, documentation, and production security/privacy/reliability hardening. Outcome: a secure, polished, production-ready Discord integration where communities discover and back FablePool projects from their own servers, while fablepool.com stays the canonical system of record for identity, credits, billing, ledgers, project state, moderation, and artifacts.

FablePool crowdfunds ambitious AI builds in public, and Discord is where many open-source, AI, developer, creator, and research communities already live. A native Discord bot lets FablePool projects be discovered, followed, discussed, and backed where the relevant communities already are — without forcing everyone into a single official FablePool server. This matters because projects are often funded by niche communities: open-source finance tooling might be backed by quant, trading, fintech, and OSS servers; AI developer tools by AI-engineering servers; scientific software by research communities. Meeting communities in their own servers helps creators build momentum, keeps backers informed, and grows FablePool through community distribution. The core product idea: Discord becomes a social layer for FablePool while fablepool.com remains the canonical system of record for identity, credits, billing, ledgers, project state, moderation, and artifacts. It serves makers, open-source maintainers, AI builders, Discord community owners, backers, reviewers, and moderators alike.

Produce a production-oriented technical design for the Discord integration, including system boundaries, Discord app permissions, OAuth install flow, FablePool canonical-system responsibilities, data models for guilds/channels/project bindings/account links/follows/notification settings/analytics/audit logs, REST or internal API contracts, event contracts, idempotency strategy, security threat model, privacy model, rollout plan, and acceptance criteria for later implementation milestones.

Implement the core Discord bot service scaffold with slash-command registration, Discord gateway/interactions handling, secure OAuth install and authorization flow, least-privilege permission checks, guild installation records, token storage/rotation interfaces, environment configuration, logging, test harnesses, and initial deployment documentation. This milestone establishes the runnable bot without project-specific features beyond installation and health checks.

Implement the first usable read-only integration: authorized server admins can connect a guild to FablePool, bind one project to one channel, unbind it, and view binding state. Add /fablepool project, /fablepool status, and /fablepool help with rich embeds sourced from canonical FablePool project APIs. Include permission checks, safe error handling, tests, and seed/admin tooling for local verification.

Implement event ingestion from FablePool for project lifecycle updates and deliver read-only rich embeds into bound Discord channels. Cover plan generated, review submitted, approved/rejected/sent back, milestone changes, funding target changes, milestone started/completed, artifact released, build-log posted, cancelled/archived, and refund/credit project events. Include webhook signature verification or equivalent event authentication, retry behavior, duplicate-event protection, delivery logs, and tests.

Implement Discord-native project discovery commands and interaction components: /fablepool discover, /fablepool search, featured, trending, nearly-funded, and recently launched project browsing. Produce polished embeds showing title, summary, funding target, credits raised, percent funded, current milestone, backer count, artifact license, project status, and canonical fablepool.com links. Add View project, Follow, Back, and Share buttons as non-mutating placeholders where later milestones will attach behavior.

Implement /fablepool milestones, /fablepool funding, and /fablepool buildlog with paginated embeds, select menus, buttons, modals where appropriate, ephemeral/public response choices, consistent visual styling, accessibility-conscious formatting, rate-limit-aware pagination, and robust handling of large projects and long build logs. Include UX copy, reusable embed builders, component state validation, and tests.

Implement secure account linking using short-lived signed URLs, CSRF protection, explicit consent screens on fablepool.com, account-link persistence, revocation/unlink flows, account-change handling, multi-server behavior, Discord account replacement safeguards, and privacy-preserving linked-state checks. Add /fablepool settings link/unlink surfaces, audit logs, tests, and documentation. The bot must not handle billing credentials or expose private balances publicly.

Implement project follow/unfollow flows from Discord buttons and commands, private DM or ephemeral update preferences, backer-only/private update eligibility checks through FablePool APIs, notification opt-in/out management, handling for users in multiple guilds, graceful DM failure behavior, and follower analytics events. Include consent-aware UX, preference storage, tests, and documentation.

Implement /fablepool back project:<id> amount:<credits> with an ephemeral confirmation embed and Confirm, Change amount, View project, and Cancel actions. Integrate with canonical FablePool credit ledger and project funding pool APIs so website and Discord pledges share the same source of truth. Add linked-account checks, insufficient-credit top-up links, secure account-link prompts, idempotency keys, Discord retry/double-click protection, receipt links, public funding total refresh, fraud/suspicious-activity hooks, and extensive tests for duplicate prevention and failure recovery.

Expand from the MVP binding model to support many projects per guild, one project appearing across many guilds subject to project-owner permission and anti-spam rules, channel-level configuration, server-level defaults, notification filtering, quiet mode, digest mode, major-updates-only mode, and project-owner approval controls. Include configuration commands, persistence migrations, conflict handling, background digest generation, tests, and admin-facing operational notes.

Implement role-aware behavior across Discord server admins, project owners, builders, backers, reviewers, moderators, followers, and general members. Enforce authorization for bind/unbind, settings changes, admin actions, and promotion visibility. Add anti-spam limits, project promotion eligibility checks, abuse report flows, misleading-promotion reporting, suspicious backing signals, private-data redaction, and tests proving unauthorized users cannot impersonate owners, alter funding, or post fake build-log entries.

Implement FablePool admin surfaces and backend controls for viewing installed guilds, project/channel bindings, integration health, notification delivery status, and moderation state. Add actions to disable a server integration, block a guild, disconnect a project from Discord, bar a project from bot promotion, review abuse reports, and inspect audit logs. Include secure admin authorization, audit trails for all admin actions, tests, and operator documentation.

Implement analytics for Discord-sourced project views, button clicks, follows, backing attempts, completed backings, active guilds/channels, notification delivery, and view-to-back conversion without exposing user-level financial data to server admins. Add event taxonomy, attribution rules, privacy safeguards, aggregation views, retention guidance, opt-out or minimization hooks where applicable, tests, and documentation for interpreting metrics.

Harden the full integration for production with rate limiting, interaction replay protection, secure error handling, observability, alerting, retry queues, dead-letter handling, data migration checks, load-test plans, end-to-end test scenarios, security review checklist, operational runbooks, deployment guides, rollback procedures, and complete user/admin documentation covering install, connect, bind, notifications, commands, backing, account linking/unlinking, permissions, troubleshooting, and the security model.