trainingsites/campus-ai-os/community-pulse

Community Pulse

Daily community engagement — post discussions, highlight wins, monitor questions, and keep the community active. Works with any community platform or outputs to files.

Setup Required

Kernel preamble §1 applies: references/kernel-preamble.md.

Before You Start

1. Read the resolved icp context — who the community members are
2. Read the resolved brand context and the resolved voice context — community voice
3. Read the resolved offers context — current programs (informs discussion topics)
4. Read the resolved connections context (resolve per CONTEXT_CANON (.campus-os/context-files.md, else the plugin's templates/context-files.md): founding name → canon → alias, each also matched case-insensitively before the next; never hard-code a filename) — check if a community platform is connected
5. Check the relevant employee's memory.md for recent community activity

Modes

Morning Pulse

Run at the start of the day. Creates proactive engagement content.

Evening Sweep

Run at the end of the day. Reviews what happened and flags items.

Morning Pulse Steps

Step 1: Discussion Prompt

Create a discussion post for the community:

• Tie to a current topic, recent lesson, or common challenge
• Ask an open-ended question that invites sharing
• Keep it short — 2-4 sentences max

Discussion prompt formats (rotate):

• "What's one thing you're working on this week?"
• "Quick win: share something that worked for you recently"
• "Hot take: [opinion related to niche]. Agree or disagree?"
• "Question of the day: [specific question about their work]"
• "Resource share: what's one tool/resource you'd recommend for [topic]?"

Step 2: Win Highlight (if applicable)

If any member wins or milestones are noted in memory:

• Write a celebration post highlighting the win
• Tag or mention the member (if platform supports it)
• Frame it as inspiration for others

Step 3: Content Share

Share one valuable piece of content:

• A recent output from your content or teaching staff (blog, lesson, resource) in outputs/
• A relevant insight from the morning brief
• A tip tied to a current offer or program

Evening Sweep Steps

Step 1: Activity Review

If community platform is connected:

• Check for unanswered questions or posts
• Check for new member introductions
• Check engagement on today's posts

If not connected:

• Ask the owner: "Any community activity today I should know about?"

Step 2: Response Drafts

For any unanswered questions:

• Draft helpful responses in the owner's voice
• Flag any questions that need the owner's direct input

Step 3: Tomorrow Prep

• Note any topics that emerged from today's discussions
• Suggest tomorrow's discussion prompt topic
• Log community activity to memory

Output

If community platform connected: Post directly (with owner confirmation) If not connected: Save to outputs/YYYY-MM/social/community-pulse-[date].md

Log all community activity to the relevant employee's memory.md.

Rules

• Discussion prompts must be genuinely interesting — not corporate engagement bait
• Never post the same prompt format two days in a row — rotate
• Celebrate wins publicly, address problems privately
• Match the owner's community voice — casual, encouraging, real
• If engagement is low, don't escalate posting frequency — improve post quality