feat(herald): proactive daily content engine#309
Merged
Conversation
8-task TDD plan giving HERALD a proactive daily content engine: GitHub activity digest -> weekly theme calendar -> HERALD LLM draft -> enqueue to the existing approval queue. Builds on the queue->approval->publish pipeline; generation only writes the DB (never calls the X API). First workstream of the T3 growth-phase refresh (sip-protocol spec 2026-06-02).
…ins, doc corrections
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Gives HERALD a proactive daily content engine: a cron drafts one original tweet/day from a weekly theme calendar + a live GitHub activity digest (via the HERALD LLM), and enqueues it to the existing approval queue. You approve in the Command Center HeraldView; the existing
checkScheduledPostspoller publishes approved posts. Generation is DB-only — it never calls the X API.New
packages/agent/src/herald/content/submodule (6 modules + 23 tests) wired into the HERALD startup block:calendar.ts— day-of-week → content themegithub-digest.ts— commits/PRs/releases/stars, graceful degradationprompt.ts— HERALD content-drafting voice + draft promptgenerator.ts— LLM draft viachat(),tools: [](no wallet registry), code-point-safe 280 truncationenqueue.ts—type='content'pending row + same-day guardcron.ts— orchestrator + opt-in hourly cron, gated on kill-switch + budgetSafety
HERALD_CONTENT_CRON_ENABLED(default off)pausedpending; nothing auto-publishes (keepHERALD_AUTO_APPROVE_POSTS=false)First workstream of the T3 Superteam growth-phase refresh. Plan:
docs/superpowers/plans/2026-06-02-herald-content-engine.md.Test Plan
pnpm --filter @sipher/agent test— 1685 passed / 2 skipped (pre-existing Torque e2e)pnpm typecheck— clean@sipprotocolX OAuth creds +HERALD_CONTENT_CRON_ENABLED=trueon the VPS; confirm a draft lands in HeraldView for approval