morning-brief

name	morning-brief
description	Daily CEO summary posted each morning. Reads MEMORY.md and active issues, summarizes overnight News Researcher output, lists active PRs, and flags any blockers. Produces a comment in the root company issue.

Morning Brief

The morning brief is the CEO's daily situational awareness document. It runs at the start of each day as part of the heartbeat cadence.

What to Read First

Before writing the brief, read:

1. D:/QA_A/artstroy/.claude-memory/MEMORY.md (or the equivalent Paperclip memory store)
2. D:/QA_A/artstroy/docs/project_notes/ — specifically key_facts.md for any config changes
3. Open issues assigned to any agent in this company
4. New topic briefs created by News Researcher since yesterday
5. Active PRs on AZANIR/artstroy (via GitHub API using GH_TOKEN)

Output Format

Post as a comment on the root company issue:

## Morning Brief — {YYYY-MM-DD}

### Active PRs
- [{branch}]({url}) — {assignee}, {status}, {age in days}

### News Researcher Queue
- {count} topic briefs pending EIC review
- Top topic: "{title}" (score: {score}/15)

### Active Issues
| Agent | Issue | Status | Blockers |
|---|---|---|---|
| {agent} | {title} | {status} | {blocker or —} |

### Overnight Signals
- {any CVE alerts, urgent escalations, or anomalies from the past 24h}

### Today's Priority
1. {highest-priority unblocked item}
2. {second priority}

_Generated by CEO heartbeat at {time}_

Rules

• Keep it short: the brief is a scan, not a report. If a section has nothing to show, write "— none" and move on.
• Flag real blockers only: a PR in review for 1 day is not a blocker. A PR in review for 4+ days is.
• No decisions in the brief: the brief surfaces facts; decisions happen via routing issues.
• One brief per day: if already posted today, skip.
• After posting the brief, check the issue queue for any unrouted work and route it via the standard CEO routing logic.