Skip to content

docs(plans): C3 exit record under §3C (readiness plan) #1708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lilyshen0722 merged 1 commit into from
Sep 16, 2026
+1 −1
Merged

docs(plans): C3 exit record under §3C (readiness plan) #1708

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/plans/production-readiness-and-selling-2026-09-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ Selling before 6 is true sells a liability. Everything below is ordered by that.
|---|---|---|---|
| C1 The funnel is not measured weekly | 49 signups / 30 d known only because someone ran a script today | A scheduled weekly report: signup → typed → got a reply → connected a channel → day-2 return → day-7 active, with the numbers in a pod, not a chat log. The script in this plan's appendix is the seed | GTM + Sharpen |
| C2 Hosted default caps at 1 agent | `DEFAULT_AGENTS_PER_USER = 1` | Decide the free/Pro split of hosted agents (D2) and make the cap the pricing table, not a beta constant | **Sam** |
| C3 Channel connect in < 2 minutes | Telegram proven; Slack/Discord install UX untested by a stranger; 6 connected channels total | One recorded stranger run per channel (Telegram, Slack, Discord) from the Connectors page, timed; fixes filed from the recording | Connectors + UX Lead gates |
| C3 Channel connect in < 2 minutes | Telegram proven; Slack/Discord install UX untested by a stranger; 6 connected channels total | One recorded stranger run per channel (Telegram, Slack, Discord) from the Connectors page, timed; fixes filed from the recording. **C3 exit record (stranger run 2026-09-12, throwaway account, commonly.me):** timings as they stand — Telegram connect → enable code 2m04s wall clock (~10 s net); code → first relay not reached (the live build did not name the bot; no Telegram account on the run); Slack not runnable (not enabled on commonly.me); Discord not runnable (not on the list). Eight stumbles, all on main: TASK-021 bot handle unset in the build #1699 `50dea44d`; TASK-022 signup did not sign the user in #1701 `d7814143`; TASK-023 code half, one definition of Slack enabled #1700 `c99261c2`; TASK-025 pod picker label #1702 `5456486f`; TASK-026 enable-code copy and expiry #1704 `089f52ec`; TASK-027 Telegram card copy #1705 `3d2bc281`; TASK-028 zero-pod state #1706 `3e44ad97`; C3-9 connector row crush #1703 `25c45c26`. Two rows stay with Sam: TASK-023's credential half (the Slack OAuth app and its SM values) and TASK-024 (Discord on the list). None of it is live until the next Deploy Dev; the Telegram enable step is re-run after it, and the Slack and Discord timings wait on Sam's two rows | Connectors + UX Lead gates |
| C4 The Tools page and approval card (pieces 3–4) | in flight tonight | Land #1667/#1670/#1669; then the same stranger run for "grant a tool → approve an action" | Connectors |
| C5 Empty states and the second visit | scripted starter workspace shipped 07-03; unmeasured since | C1's day-2 number decides whether this is a gap | GTM |

Expand Down
Loading