lvl0/buckets
1
0
Fork 0
Code Issues 11 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Should we only allow one scenario per account? #22

New issue
Closed
opened 2026-03-29 04:16:44 +02:00 by myrmidex · 1 comment
myrmidex commented 2026-03-29 04:16:44 +02:00
Owner
Copy link

Seems illogical to have multiple scenarios, since we don't force the user to save the drip.

Seems illogical to have multiple scenarios, since we don't force the user to save the drip.
myrmidex added the
question
 label 2026-03-29 04:16:44 +02:00
myrmidex self-assigned this 2026-03-29 04:16:44 +02:00
myrmidex added a new dependency 2026-03-29 04:16:58 +02:00
#3 First-time onboarding wizard
myrmidex commented 2026-03-29 23:36:48 +02:00
Author
Owner
Copy link

Decision: Yes, one scenario per account.

Reasoning:

  • The app's core value is the distribution pipeline, not scenario management
  • The preview/distribute flow is stateless-first — multiple scenarios imply saved state management that doesn't match the design
  • YAGNI — can always add later if there's demand

Impact:

  • Remove multi-scenario scaffolding (commented-out routes, Index page, unused CRUD actions/requests) → cleanup ticket #24
  • #3 (setup wizard) simplifies to onboarding-only flow
  • #10 (stream design) simplifies — no cross-scenario concerns
  • #8 wording update — "scenario setting" becomes "app setting" (functionally unchanged)
**Decision: Yes, one scenario per account.** Reasoning: - The app's core value is the distribution pipeline, not scenario management - The preview/distribute flow is stateless-first — multiple scenarios imply saved state management that doesn't match the design - YAGNI — can always add later if there's demand **Impact:** - Remove multi-scenario scaffolding (commented-out routes, Index page, unused CRUD actions/requests) → cleanup ticket #24 - #3 (setup wizard) simplifies to onboarding-only flow - #10 (stream design) simplifies — no cross-scenario concerns - #8 wording update — "scenario setting" becomes "app setting" (functionally unchanged)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release/v0.2.0
v0.2.0
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
research

   
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
research
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
myrmidex
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#3 First-time onboarding wizard}
lvl0/buckets
Reference: lvl0/buckets#22
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?