Agents
Pipeline
Daily Workflow
Routing Rules
Dashboard & API
Data & Schema
File Structure
Agent Team
Four specialized Claude Opus agents with persistent memory, coordinated through an orchestrator.
📋
Content Strategist
Plans what gets posted, when, and why
Claude Opus Persistent Memory
Responsibilities
- Weekly content themes and daily slot assignments
- Content calendar and campaign planning
- Pillar balance and content mix optimization
- Narrative research for content angles
- Performance review and strategy adjustments
Templates
- Content Pillars Framework
- Weekly Plan, Daily Brief, Calendar
- Campaign Planner, Performance Review
Reads From
- knowledge/ (features, tokenomics, narratives)
- content/calendar/ (existing plans)
- output/analytics/ (performance data)
- brand/ (voice, terminology, do-not-say)
✍
Copywriter
Turns strategy briefs into polished tweet copy
Claude Opus Persistent Memory
Responsibilities
- Write tweets, threads, and QRT copy
- Maintain brand voice consistency
- Evaluate visual need per post
- Delegate to graphic-designer when needed
- Produce multiple draft variations
Output Formats
- Single tweet (280 chars max)
- Thread (4-8 tweets, numbered "1/" format)
- YAML frontmatter + markdown body
Key Constraint
- Never financial advice or price predictions
- Every tweet must pass "would I bookmark this?" test
📊
Data Analyst
X performance analytics and trend discovery
Claude Opus Persistent Memory
Responsibilities
- Pull X API v2 metrics (engagement, reach, growth)
- Analyze post performance and content types
- Identify trending topics and opportunities
- Build interactive HTML dashboards
- Surface strategic recommendations
X API Access
- Bearer token auth (read-only analytics)
- Endpoints: user info, tweets, search, mentions
- Rate-limit aware, cache-first approach
Analysis Framework
- Observation (data) → Insight (why) → Action → Impact
🎨
Graphic Designer
Evaluates visual need and creates brand graphics
Claude Opus Persistent Memory
Responsibilities
- Assess whether each post needs imagery
- Create graphics matching brand identity
- Design announcements, infographics, thread openers
- Maintain visual consistency across campaigns
Brand Palette
- Background: #0a0a0a (near-black)
- Accent: #00c9a7 (teal/cyan)
- Glow effects, portal rings, polygonal style
- Format: 1200x675px (16:9)
Invocation
- Usually called BY the copywriter (auto-delegation)
- Can be called directly for standalone requests
Content Production Pipeline
The standard flow from strategy to published tweet.
Agent 1
Content Strategist
→
→
Agent 3 (optional)
Graphic Designer
→
→
Feedback loop
→
→
Feeds Back To
Content Strategist
Post Status Flow
Every post transitions through these states.
Pending
→
Draft
→
Approved
→
Published
Rejected drafts return to Pending for rework
Content Pillars
All content maps to one of five strategic pillars. No pillar should exceed 35% of weekly output.
📡
Signal Intelligence
AM-1 primary
25-35% weekly
📦
Product Showcase
AM-2 primary
20-25% weekly
📚
Education & Depth
PM-1 primary
8-12% weekly
👥
Community & Culture
PM-2 primary
20-25% weekly
🌐
Ecosystem & Narrative
FLEX primary
10-15% weekly
Daily Content Workflow
The four-phase cycle that runs every day. Target: 3-5 posts per day.
- Analyst Scans overnight market activity, narrative shifts, competitor posts
- Analyst Delivers morning brief: top 3 relevant developments + active narratives
- Strategist Selects daily themes, assigns content to 5 slots (AM-1, AM-2, PM-1, PM-2, FLEX)
- Strategist Outputs content brief for each slot (type, theme, angle, key points, CTA)
- Copywriter Generates tweet/thread copy for each content slot
- Designer Creates graphics for posts that need visual enhancement
- System Drafts saved to
content/drafts/ and schedule.json (status: draft)
- Human Reviews drafts in dashboard, approves or rejects each post
- Auto-Publisher Hourly cron checks for approved posts whose scheduled_time has passed
- X API Uploads media (if any) then posts tweet or thread via OAuth 1.0a
- Engagement Monitors replies and mentions within first 2 hours of publishing
- Engagement Drafts responses to meaningful community interactions
- Analyst Pulls post performance metrics via X API v2
- Analyst Logs insights to agent memory (baselines, patterns, top performers)
- Strategist Performance data feeds into next morning's planning cycle
Engagement Loop
Continuous community monitoring and response workflow.
- Engagement High priority (1hr): Direct questions about Tracehound, FUD/misconception correction
- Engagement Medium priority (4hr): Community sharing Tracehound, relevant threads for value-add
- Engagement Low priority: General crypto discussions (opportunistic)
- Human Escalation triggers: Price/investment Qs, partnerships, legal, security, media, wallet data, harassment
Narrative Monitoring
Crypto narrative tracking for timely content opportunities.
- Real-time: Token unlocks, major on-chain movements, viral narratives
- Hourly: Trending topics on Crypto Twitter, sentiment shifts
- Daily: Competitor content audit, narrative momentum assessment
- Weekly: Narrative lifecycle review (emerging → active → peaking → fading)
- Content windows: Breaking (0-2hr) → Active (2-24hr) → Fading (24-72hr) → Dead (72hr+)
Agent Routing Rules
How user requests are matched to the correct agent.
→ Content Strategist
Planning, calendars, strategy, narrative research
plan contentcontent calendarwhat should we postweekly plancampaign plancontent briefcontent ideaswhat topicsengagement dropping
→ Copywriter
Writing tweets, threads, QRTs, announcements
write a tweetdraft a threadwrite copywrite a postcreate a tweet aboutwrite an announcementdraft this
→ Data Analyst
Performance analytics, dashboards, trend discovery
how are we performingengagement metricsanalyticsdashboardperformance reporttrending topicsreach droppedour best posts
→ Graphic Designer
Visual assessment, graphic creation, brand imagery
create a graphicdesign an imagemake a visualneed an imagecreate a banner
Multi-Step Routing Logic
- Topic/angle is clear → Go directly to Copywriter
- Strategy decisions needed first → Start with Strategist then pass brief to Copywriter
- Performance data needed → Start with Analyst then pass findings to Strategist
- Independent tasks → Run agents in parallel (e.g., analyst + strategist simultaneously)
Dashboard & REST API
Node.js + Express web dashboard with approval workflow and X API posting.
app.tracehound.ai
Dashboard URL
API Endpoints
| Method | Path | Action |
|---|
| GET | /api/posts | List all posts (filter by ?status= or ?date=) |
| GET | /api/posts/:id | Get single post by ID |
| PUT | /api/posts/:id | Update post content or fields |
| POST | /api/posts/:id/approve | Move status: draft → approved |
| POST | /api/posts/:id/reject | Move status: draft → pending |
| POST | /api/posts/:id/publish | Publish to X (approved → published) |
| POST | /api/posting/publish-due | Batch publish all approved posts past due |
| GET | /api/stats | Aggregate counts by status |
X API Integration
- Single Tweet: Upload media (if image_path set) → POST /2/tweets with text + media_id → Store published_id
- Thread: Post tweet 1 (with media) → get ID → Post tweet 2 as reply → get ID → chain → Store all IDs
- Media Upload: INIT (declare) → APPEND (5MB chunks) → FINALIZE (complete) → Return media_id_string
Auto-Publishing Schedule
- Scheduled task runs
publish-due.js every hour
- Script reads schedule.json, filters: status=approved AND scheduled_time ≤ now
- For each due post: upload media → post to X → update status to published
- Prints summary to stdout (published count, failed count)
Data Schema
The schedule.json schema — single source of truth for all posts.
{
"id": "w1-mon-am1",
"date": "2026-04-14",
"day": "Mon",
"slot": "AM-1",
"scheduled_time": "2026-04-14T08:00:00Z",
"type": "tweet" | "thread",
"pillar": "signal",
"title": "Fear & Greed at 46 days",
"content": "Tweet text...",
"thread_tweets": ["1/...", "2/..."],
"image_path": null | "path/to/image.png",
"status": "pending" | "draft" | "approved" | "published",
"published_id": null | "X tweet ID",
"published_thread_ids": [],
"created_at": "ISO timestamp",
"updated_at": "ISO timestamp"
}
Slot-to-Time Mapping
| Slot | UTC Time | Primary Pillar | Purpose |
|---|
| AM-1 | 08:00 UTC | Signal Intelligence | Timely market observations |
| AM-2 | 09:00 UTC | Product Showcase | Feature highlights and use cases |
| PM-1 | 14:00 UTC | Education & Depth | Threads and deep-dives |
| PM-2 | 16:00 UTC | Community & Culture | Engagement and relationship building |
| FLEX | 12:00 UTC | Ecosystem & Narrative | Reactive/trending content |
Environment Variables (.env)
X_BEARER_TOKEN=AAAA...
X_API_KEY=...
X_API_SECRET=...
X_ACCESS_TOKEN=...
X_ACCESS_TOKEN_SECRET=...
DASHBOARD_PORT=3000
File Structure
Complete project directory tree.
tracehound-x-agent/
CLAUDE.md
.env
.claude/
agents/
content-strategist.md
copywriter.md
data-analyst.md
graphic-designer.md
agent-memory/
content-strategist/ copywriter/ data-analyst/ graphic-designer/
launch.json
agents/
README.md
content-strategist/
config.md content-pillars.md weekly-plan-template.md
daily-brief-template.md calendar-template.md
campaign-planner-template.md performance-review-template.md
copywriter/
config.md
engagement/
config.md
analyst/
config.md
brand/
voice-guide.md terminology.md do-not-say.md visual-guide.md
logo-profile-pic/
knowledge/
tracehound-features.md tokenomics.md competitors.md crypto-narratives.md
prompts/
tweets/ market-observation.md product-highlight.md
threads/ educational.md
replies/ community-response.md
campaigns/ launch-campaign.md
workflows/
daily-content.md engagement-loop.md narrative-monitor.md
content/
schedule.json
calendar/
drafts/
approved/
published/
dashboard/
server.js package.json
lib/ schedule-store.js x-api-client.js media-upload.js
routes/ api.js posting.js
scripts/ publish-due.js
public/ index.html css/styles.css js/dashboard.js
context/
Tracehound Whitepaper.pdf Tracehound Pitch Deck.pdf
output/
analytics/ reports/ architecture.html