goviralbro: Command for Claude Code

/viral:update-brain — Brain Evolution Protocol

You are running the Viral Command brain update. Your job is to analyze recent performance data and evolve the system-managed sections of the agent brain — learning what works so future content recommendations get smarter.

This command is the feedback loop. It's called after /viral:analyze collects new performance data, or manually when the user wants to recalibrate.

---

⛔ DO NOT MODIFY — User-Managed Fields

The following fields are owned by /viral:onboard and must NEVER be changed by this command:

• identity (name, brand, niche, tone, differentiator)
• icp (segments, pain_points, goals, platforms_they_use, budget_range)
• pillars (content pillar definitions)
• platforms (research, posting, api_keys_configured)
• competitors (monitored creators)
• cadence (weekly_schedule — but optimal_times CAN be updated)
• monetization (primary_funnel, secondary_funnels, cta_strategy, client_capture)

If you touch these fields, you are breaking the system. The only exception is cadence.optimal_times, which is data-driven and updated by analysis.

---

Phase A: Read Current State

Read all data sources to understand what's available:

@data/agent-brain.json
@data/insights/insights.json
@data/hooks/hook-repo.jsonl
@schemas/agent-brain.schema.json

Also scan for recent analytics entries:

@data/analytics/

Check for new data:

1. Read metadata.last_analysis from the brain — this is the last time an update ran
2. Check data/analytics/ for entries newer than last_analysis
3. Check data/hooks/hook-repo.jsonl for entries with performance data

If no new data since last analysis:

No new performance data since last brain update ({last_analysis date}).

Run /viral:analyze first to collect fresh analytics,
or add performance data manually to data/analytics/.

Exit without changes.

If new data exists, summarize what's available:

Brain Update Data Available
════════════════════════════════════════

Last brain update: {last_analysis or "never"}
New content analyzed: {count} pieces
Hook data available: {count} hooks with performance metrics
Platforms with data: {list}

Proceeding to analysis...
════════════════════════════════════════