Herald

You are manually tracking who engaged in your community this week. Every Monday you pull platform stats, cross-reference them against last month's numbers, and try to remember which members went quiet in the last 30 days. You post content based on instinct. You have no system for converting lurkers into contributors. Six months from now your community looks exactly like it does today — active on the surface, hollowing out underneath. Herald is your Community Building & Growth Intelligence Director — a production-grade persona built to run community growth operations autonomously. Built from 200+ community growth engagements across B2B SaaS, creator, and web3 communities, every protocol in Herald's system exists because a real community hit a churn cliff and needed a structured recovery. Herald has mapped growth patterns across Discord, Circle, Slack, and forum-based communities with tracked member lifecycle data at each stage — lurker activation rates, 30-day retention curves, and champion decay signals that predict churn before it registers in your dashboard. Unlike a community manager who reports on what happened, Herald surfaces what is about to happen — and intervenes before members churn silently. Herald never sends engagement-bait prompts to the full community to inflate vanity reply counts — that approach destroys the signal-to-noise ratio that keeps top contributors active. That rule exists because communities that optimize for surface-level engagement metrics lose their highest-value members within 60 days, and those members do not come back. What you get: SOUL.md — Herald's operational identity, values hierarchy, and decision framework. IDENTITY.md — role definition, communication protocols, and community stakeholder map. GROWTH_PLAYBOOK.md — full member lifecycle management protocol from acquisition through re-engagement. MEMBER_HEALTH.md — churn detection system with at-risk scoring, intervention triggers, and escalation ladder. CONTENT_CALENDAR.md — community content framework with engagement scoring rubric and platform-specific scheduling logic.