docs: add outreach SOP for admin pipeline#825
Merged
Conversation
Contributor
Author
|
Context: this is intentionally docs-only and scoped to the CEO question in #820.\n\nIt does not change send behavior. It documents the intended use of the existing outreach endpoints so future ops/marketing work has a canonical in-repo reference:\n- status check first\n- load targets into D1\n- inspect pending/stats\n- send a small batch\n- verify outcome\n\nThis should reduce confusion around whether the outreach endpoints are meant to be used: yes, as the D1-backed/auditable path. |
This was referenced Mar 17, 2026
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
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.
Summary\n- add a canonical
docs/ops/outreach-sop.mdfor the admin outreach pipeline\n- document the intended purpose of the outreach endpoints and the sequence for using them\n- update the legacy cold email workflow doc to point at the SOP as the preferred operational path\n\n## Why\nThe CEO asked in #820 whether the outreach endpoints are actually used and what their purpose/SOP is. This PR answers that in-repo with a concrete operator guide tied to the current Bearer-auth/api/admin/*contract.\n\n## Validation\n-npm test --workspace=apps/worker -- admin.test.ts