8000 [Feature] BAP-CARES integration prompt · Issue #282 · jra3/mulm · GitHub
[go: up one dir, main page]

Skip to content

[Feature] BAP-CARES integration prompt #282

Closed

Description

@jra3

Current delivery plan — 2026-10-15

Delivery plan: #558; launch verification: #564.

Implement the existing opt-in design using the current lifecycle and independent CARES registrations:

  • Show the prompt on a Member-visible Approved Submission surface; committee approval is not itself a Member confirmation page.
  • Only offer it for an eligible BAP Species without an existing registration for that Member. Validate and preselect that Species in the existing registration flow.
  • Respect the CARES visibility gate: ordinary Members must not receive a link to an inaccessible flow while the registry is admin-only. Verify intended Member behavior on controlled staging before launch.
  • Preserve the existing dismiss/Maybe Later behavior in the design comment. Never auto-register, change awarded points, or tie the BAP CARES bonus to registration.
  • Verify eligible/ineligible Species, already registered, unapproved Submission, foreign viewer, dismissal, Species preselection and gate behavior.

Blocked by: None for implementation behind the gate. Member exposure is coordinated by #564.

Earlier requirements and design

Overview

Prompt members to register for CARES when they breed a CARES species through BAP.

Parent: #276

Phase 2 - Activities

Requirements

  • FR7.1: After BAP submission is approved for a CARES species, prompt member to register
  • FR7.2: Prompt appears on confirmation page and/or notification
  • FR7.3: Link directly to CARES registration flow for that species
  • FR7.4: Do not auto-register - member must explicitly opt in

Trigger Conditions

  • BAP submission approved
  • Species is marked as is_cares_species
  • Member has not already registered this species for CARES

UX

  • Non-intrusive prompt/banner on approval confirmation
  • Clear CTA to register for CARES
  • Option to dismiss/ignore

Acceptance Criteria

  • BAP approval for CARES species triggers registration prompt
  • Prompt links to registration flow with species pre-selected
  • Prompt only shows if not already registered
  • Member can dismiss prompt

Activity

  1. added
    enhancementNew feature or request
    ui/uxUser interface and user experience improvements
    on Jan 21, 2026
  2. jra3 commented on Jan 21, 2026

    @jra3
    OwnerAuthor

    UI/UX Design

    Prompt Component

    Inline banner (not modal) - matches existing status panel patterns

    ┌────────────────────────────────────────────────────────┐
    │ 🐟 This is a CARES conservation species!               │
    │                                                        │
    │ Help preserve [Species Name] by registering for the   │
    │ CARES Fish Preservation Program.                      │
    │                                                        │
    │ [Register for CARES]              [Maybe Later] [✕]   │
    └────────────────────────────────────────────────────────┘
    

    Style: bg-green-50 border-l-4 border-green-400 (conservation theme)

    Placement

    On BAP submission approval confirmation page:

    • After the "Submission Approved" success message
    • Before any navigation links

    Dismiss Behavior

    Three options:

    1. "Register for CARES" - Navigate to registration flow with species pre-selected
    2. "Maybe Later" - Dismiss temporarily, show again on next CARES species approval
    3. "✕" (close) - Same as "Maybe Later"

    No global opt-out for now - CARES prompts are infrequent enough that a preference isn't needed.

    Pre-Selected Flow

    Pass species via URL parameter:

    • /cares/register?species={group_id}
    • Registration form auto-selects the species
    • Species dropdown is pre-filled but can be changed

    Trigger Conditions

    Show prompt when ALL of:

    • BAP submission status changes to "approved"
    • Species has is_cares_species = true
    • Member does NOT already have a CARES registration for this species
  3. added a commit that references this issue on Feb 22, 2026
    709a108
  4. added
    priority:mediumMedium priority - important but not urgent
    ready-for-agentFully specified, ready for an AFK agent
    on Oct 16, 2026