PEP gets used in more than one place, so problems show up in more than one place. They all funnel into one board we actually fix from.
Slack — the main way churches use PEP. A volunteer says "the vocal cut out" in their channel. Primary, zero-friction; they're already there.
The app — internal testers (Marlon) and app users hit issues directly.
Marlo — the analysis layer. It reads the interaction logs from both Slack and the app and surfaces problems automatically: failed commands, and requests PEP couldn't fulfill (capability gaps). Ask it "what failed this week?" or "what did people ask for that PEP couldn't do?" — see What you can ask Marlo.
None of these is the issue tracker. They're inputs.
Anything worth fixing becomes a tracked item in the Pep Issues workspace. Someone promotes a signal (a Slack report, an app finding, a Marlo result) into an issue using the template. It stays there, visibly, until it's closed.
Lanes: Inbox (new / triaged) → In progress (being fixed) → Closed (done). Duplicate the template, title it [Broken/Rough/Note] short summary, and move it across as it's worked.
Slack, the app, and Marlo are the signals; triage promotes anything worth fixing into Pep Issues, which is where it's tracked until it's closed.