Slack — auth/accounts scope clarification (2026-06-29)¶
Source: Slack #cs-lewis thread, 2026-06-29. Between Saurabh Kumar (eng) and Lina Wiezkowiak (delivery lead, CS Lewis build).
Link: https://fueled.slack.com/archives/C0B6838LX4J/p1782724111903579
Re: the "Product Features" Notion DB (e9f4dccd9d8b8315b895816213227423) — auth/account/gate items marked High priority with no MVP-vs-Phase-2 segmentation (the tension flagged in 05-feature-backlog.md).
Thread (verbatim)¶
Saurabh Kumar:
quick question on the feature doc! You've got auth/account/gates marked as High priority, but it's not clear to me whether those are meant to be part of the 14 week deliverable. I don't want to assume either way, so figured I'd check with you directly. Are those in scope for the 14 weeks, or are they High priority for a later phase?
Lina Wiezkowiak:
good questions and thanks for reaching out directly. The Feature doc was a quick and dirty stab on Thursday pre-client vetting to make sure we can get to a realistic roadmap and scope for the 14 week build. I need to go in an prune/clarify a few things, but to answer this specific question now, auth/account is in scope for the 14 week build, gate are not
Aka we are not monetizing content in V1 but users need to be able to make an account
Resolution¶
- Auth + account creation: IN scope for the 14-week build (V1).
- Gates: NOT in scope for V1.
- No content monetization in V1 (no paywall/subscription gating of content).
- Users must be able to create an account in V1.
Caveats¶
- The Product Features doc was a pre-client-vetting first pass; Lina still intends to prune/clarify it. Treat individual rows as provisional until she revises.
- This reverses the previously documented non-negotiable "No auth at MVP." Confirmed by the delivery lead but not yet client-vetted — flag for an ADR once locked.