Marks the signal as relevant and worth surfacing. Sets status to "approved" and moves it out of your active review queue. You can still see it by filtering for Approved. In a future version, this pushes the signal to the client's "What's New" section.
Mark Reviewed
You've read it but aren't ready to approve or dismiss. Sets status to "reviewed." Useful when triaging a batch quickly to separate "looked at" from "untouched."
Dismiss
Removes the signal from your active view with a reason (off-topic, duplicate, low quality, stale/outdated, wrong client). The reason is stored so the system can learn which signals to deprioritize. The signal is not deleted, just flagged.
Annotate
Adds a free-text note to the signal, stored in the database and fed back to the next cron run as context. Use for things like "check if this applies to Croatian producers" or "potential speaking opportunity, follow up." Annotations appear in terracotta below the signal body.
Log as Activity
Promotes a signal into the Client Activity Log when it describes something the client actually did (spoke at a conference, got published, was cited). Opens a pre-filled form where you pick a type and confirm. The activity feeds into the narrative prompt so dispatches reference what the client did, not just what happened nearby.
View Full
Expands the card to show the complete signal body, source URL, and suggested response. Click again to collapse.
0.0
0 selected
System Status
Actions reference
Trigger Analytics
Manually fires the analytics cron for the selected client. Generates a new narrative dispatch using the current signals and client brief. Same as the daily scheduled run, just on demand.
Trigger Signals
Manually fires the signal collection cron. Fetches new content from all active sources, scores relevance, and writes new signals to the database. Same as the daily scheduled run.
Client Intelligence Profile
Actions reference
Save Brief
Writes the assembled client brief JSON to the database. This is what Claude reads on every analytics run to understand the client's identity, goals, tone, and persona.
Preview Prompt
Shows exactly what Claude will receive on the next run: the assembled brief with all your edits. Useful for verifying your changes before triggering a run.
Trigger Manual Run
Fires the analytics cron immediately for this client. Generates a new narrative using the current brief and signals.
Activity Log
A chronological record of confirmed client engagements (speaking, publishing, organizing, citations, attendance). Entries come from manual logging or promoting signals via "Log as Activity" in the Signal Feed. This log feeds into the narrative prompt so dispatches can reference what the client did directly.
Narrative Review
Actions reference
Edit & Publish
Opens the narrative in an editable view alongside the original draft. Modify the text, then publish. The system stores both versions: Claude's original draft and your final version. On the next run, Claude sees the difference and learns from your edits.
Annotate
Adds direct feedback ("too formal in paragraph 2," "missed the food import angle"). Stored and injected as "previous dispatch feedback" into the next cron run.
Flag for Revision
Marks the narrative for attention. Queues your feedback for inclusion in the next scheduled run. Does not trigger an immediate rewrite.
Compare
Side-by-side view of the current dispatch next to the previous one. Shows what changed between consecutive dispatches so you can verify whether your edits and annotations are influencing output.
Archive
Removes the narrative from the active view. It stays in the database but won't clutter your working list.
Roadmap
Source Library
Actions reference
Pause
Stops the signal cron from fetching this source on its next run. The source and its existing signals remain in the database. Use when a source is producing consistently low-quality or irrelevant signals.
Resume
Re-enables a paused source so the signal cron will fetch it again on the next run.