docs(design): backlog community engagement -- Draft 1 (#31)#4
Open
akenel wants to merge 1 commit into
Open
Conversation
Draft 1 of the design for making the BL module a real two-way street with users, not just an admin tracker. Driven by Angel's framing 2026-05-23: "we need the bl to work properly end to end so its not just for me but to invite users to properly fix issues and add features they want" Covers: - Current state inventory (what's working, what isn't) - 8 gaps sized rough - User stories for Reader / Filer / Maintainer / Champion - Scope: 4 PRs in / 4 features deferred / 2 pre-existing concerns separated - Data model additions (additive only, no migrations needed for M0-M3) - API surface additions - ASCII wireframes for the proposed UI changes - Auth + ownership model proposal - 5 open questions for Stage 2 review - Milestones M0 (today, task #30 done) -> M1-M4 over ~3 weeks - Success metrics for 30-day-post-ship evaluation - Risks (scope creep, auth friction, CI schema drift) Stage-based review like we did with LP CLI: - Stage 1: per-section notes - Stage 2: fold in -> Draft 2 - Stage 3: wireframes per PR - Stage 4: locked design Recommend ship M1 (smallest, highest visual impact) BEFORE locking the full design, per LP CLI lesson on over-engineering before shipping anything. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Draft 1 design doc for making the BL module a real two-way street with users — not just an admin tracker.
Why
Your framing 2026-05-23 morning:
Task #31. Closes the bigger design conversation that task #30's API fix opened up.
Read flow
The doc follows the stage-based review pattern we proved with LP CLI:
Don't merge until Stage 4 OR until we ship M1 to validate the smallest piece is right.
Highlights
reporter_user_idbecomes "owner" for edits whilestatus==pendingRecommendation (LP CLI lesson applied)
Don't lock the full design before shipping M1. M1 is small (surface
resolution_sha+resolution_notein UI), highest visual impact, no auth/ownership complexity. Ship it, see what users do, adjust the rest.Generated with Claude Code (Opus 4.7).