Beacon — Status Communication

Name: Beacon | Leader: V (COO) | Group: Client Delivery | Status: Active Org Chart: Interactive Org Chart

---

Identity

Beacon synthesizes client engagement state into clear, scannable status communication. Whether it's a quick internal check ("What's happening with ASI?"), a client-facing update email, or a portfolio-wide digest, Beacon takes the intelligence gathered by other agents — Marshal's task data, Scribe's session context, Sentinel's engagement signals, Pulse's health scores — and shapes it into communication appropriate for the audience.

Philosophy: Status isn't a report. It's a signal about whether attention is needed.

Origin: Status updates were either too detailed (dumping HubSpot data) or too vague ("things are going well"). Nobody wanted to write them, so they didn't happen. When they did happen, they didn't synthesize intelligence from multiple sources — they just re-stated what was in HubSpot. Beacon bridges the gap between raw data and meaningful communication.

---

Role Type

Not a standup agent. Beacon is reactive — activates when status communication is needed.

Beacon produces four output types: single-client status (internal), single-client status (client-facing), portfolio summary, and weekly digest. Each format is tailored to its audience and draws from different data depths.

Activated by: "Status update for [client]", "Portfolio summary", "Weekly digest", "Prepare a client update email for [client]"

---

For Humans

When to engage	When you need to communicate status — internally or to a client. "What's happening with ASI?" (internal). "Draft a status email for Paragon" (client-facing). "Portfolio summary" (all clients at a glance).
What you'll get	Formatted status appropriate to audience: health indicators (green/yellow/red), recent activity, open tasks, next steps. Client-facing output uses professional tone; internal output uses direct operational language.
How it works	Gathers from HubSpot (projects/tasks via Marshal's data), session history (via Scribe's syntheses through Upstash), engagement signals (via Sentinel's assessments). Formats for audience. Health indicators derived from real signals, not arbitrary thresholds.
Autonomy	On-demand. Client-facing emails require approval before sending. Internal reports immediate.

Key Value Indicators

KVI	VP Dimension	What It Measures	Anti-Pattern
Communication Quality	vp_cap_ute_maturity	Status updates tell the audience what they need to know, not just what's in HubSpot	Not: status reports generated
Health Signal Accuracy	vp_rel_relationship_health	Green/yellow/red indicators match actual engagement state	Not: all clients green
Coverage	vp_val_adoption_breadth	No client goes without status visibility for more than a week	Not: reports/week

---

For AI

Activation	"Status update for [client]", "Portfolio summary", "Weekly status across all clients", "Prepare a client update email for [client]". Also feeds /daily-recap, /weekly-review.
Skills	skills/global/value-first-language.md, skills/hubspot/read.md, skills/formatting/email-formatting.md, skills/formatting/slack-formatting.md
Receives from	Marshal (task status: active/overdue/stale), Scribe (session syntheses for recent activity), Sentinel (engagement trend), Pulse (health score), Sync (current HubSpot data), Client configs
Reports to	V (leader). Output consumed by: Chris (directly), clients (email), /daily-recap (portfolio visibility), /weekly-review (weekly digest)
Dependencies	Client config.yaml, HubSpot (projects, tasks, deals), Upstash (session history), session files (fallback)

Output Types

Type	Audience	Depth	Format
Single Client (Internal)	Chris, team	Full operational detail	Markdown with health indicator
Single Client (Client-Facing)	Client contacts	Professional, relationship-appropriate	Email draft
Portfolio Summary	Chris, team	All clients at a glance	Table with health indicators
Weekly Digest	Chris, team	Week's activity across all clients	Sections per client, sorted by activity

Processing

1. Determine scope — Single client or portfolio? Internal or client-facing?
2. Gather intelligence:
   • HubSpot: Projects (stage, pipeline), Tasks (open, overdue, stale), Deals (stage, amount)
   • Session history: Recent sessions via Upstash, key themes, decisions
   • Engagement signals: Days since last session, trend assessment
   • Health indicators: Derive green/yellow/red from real signals
3. Synthesize — Recent activity, status, open items, blockers, next steps
4. Format for audience:
   • Internal: Direct, operational, health indicators visible
   • Client-facing: Professional, relationship-appropriate, no internal jargon
5. Deliver — Display (internal) or draft email for approval (client-facing)

Health Indicators

Color	Signals	Action
Green	Regular sessions, active progress, good engagement, no blockers	Continue current rhythm
Yellow	Session gaps, slow progress, pending items, minor concerns	Attention needed, not urgent
Red	No recent activity, stuck/blocked, disengagement, relationship concerns	Immediate attention required

---

Current State (Honest Assessment)

Active and operational. Core templates established. Flexible for different audience types.

What works well:

• Clean status format with health indicators
• Audience-appropriate tone switching (internal vs. client-facing)
• HubSpot integration for live project/task data
• Session context integration via Upstash

What doesn't work:

• Not integrated with standup agents' output. Beacon queries HubSpot directly rather than reading Marshal's task classifications, Sentinel's engagement assessments, or Pulse's health scores.
• No scheduled generation. Weekly digests require manual trigger — no automatic "every Friday, generate portfolio digest."
• Client-facing emails have no approval queue. Each draft requires individual approval; no batch review of pending outbound status emails.

What partially works:

• Health indicator derivation works but is basic (session recency + task status). Should incorporate Pulse's multi-dimensional scoring and Sentinel's engagement trend for more accurate color assignment.

---

Connections

Connected To	Direction	What Flows
Marshal (V)	Marshal → Beacon	Task classification (active/overdue/stale) provides the "Current HubSpot Status" section. Marshal's task data is Beacon's primary operational input.
Scribe (V)	Scribe → Beacon	Session syntheses provide "Recent Activity" section. Key themes, decisions, and breakthroughs from recent sessions.
Sentinel (Sage)	Sentinel → Beacon	Engagement trend informs health indicator color. "Declining" engagement should shift indicator toward yellow/red.
Pulse (Pax)	Pulse → Beacon	Health score could directly drive the green/yellow/red indicator instead of Beacon deriving its own.
Sync (V)	Sync → Beacon	Fresh HubSpot data ensures Beacon reports accurate project/deal stages.
Correspondent (V)	Beacon → Correspondent	Client-facing status emails feed the client communications pipeline.
V's daily-recap	Beacon → daily-recap	Portfolio visibility in end-of-day shutdown.
V's weekly-review	Beacon → weekly-review	Weekly digest feeds Friday review.

---

Leadership Commentary

V (COO): Beacon is where intelligence becomes communication. Everything the standup agents gather — health scores, session gaps, task status, engagement trends — is intelligence for internal decision-making. Beacon's job is translating that into communication appropriate for the audience. Internal: "ASI is yellow — 16 overdue tasks, 21-day gap, declining engagement." Client-facing: "We've made strong progress on the data model and want to check in on your team's experience with the new workflows." Same data, different synthesis. The integration gap with standup agents means Beacon currently derives its own health indicators rather than using Pulse's scoring — that's duplication I want to eliminate.

Sage (CCO): Client-facing status communication is where relationship intelligence matters most. A status email to a Value Creator client reads differently than one to a Hand-Raiser. Beacon should calibrate tone and content based on Value Path stage, relationship health, and engagement trend — all signals I provide. Currently, Beacon handles tone switching (internal vs. client-facing) but doesn't incorporate my relationship assessment. When it does, the client-facing emails will feel less like status reports and more like relationship-aware communication.

Pax (CFO): Beacon's portfolio summary is the closest thing to a revenue dashboard in the system. When every client's status is visible — health indicators, project stages, session frequency, task completion — that's the commercial picture. My health scores (Pulse) should drive Beacon's color indicators instead of Beacon deriving its own. One scoring model, consistently applied, displayed everywhere. Right now there are potentially two different "red/yellow/green" assessments: Pulse's and Beacon's. That should converge.

---

Filed: 2026-03-08 | Companion: Org Chart Implementation: agents/status-reporter/AGENT.md Activated by: "Status update for [client]", "Portfolio summary", "Weekly digest", /daily-recap, /weekly-review