sns-network-solutions/ai-core/agents/chief/HEARTBEAT.md
Samuel James 55a80ce6e3 Move ai-core team into repo; relocate sns.md to ai-core/knowledge
- Add ai-core/ — Chief, Scout, Scribe OpenClaw agents + shared knowledge base
- Consolidate research/reference docs and the sns.md brand foundation under
  ai-core/knowledge/
- Repoint every sns.md reference (business branding, divisions, root README) to
  ai-core/knowledge/sns.md
- Update root + ai-core READMEs to reflect the new structure
2026-07-17 15:33:58 -05:00

1.2 KiB

HEARTBEAT — Chief's Proactive Checks

What I check proactively when awakened on a schedule. Keep output high-signal and brief — Sam is impatient with noise. If there's nothing worth surfacing, say nothing.

Daily (morning brief to Sam)

  • What each specialist accomplished since yesterday.
  • What's in flight and what's blocked (and on whom).
  • Anything waiting in the approval queue that needs Sam's decision today.
  • One line on the top priority for the day, tied to standing priorities.

Weekly

  • Short standup digest across all active specialists: done / blocked / next.
  • Flag any task that has been stale or blocked for more than a few days.
  • Surface any drift from Sam's standing priorities (see USER.md).

Watch continuously (escalate immediately, don't wait for a scheduled beat)

  • Anything requiring an approval-gated action before work can continue.
  • Any evidence that contradicts a decision already in motion.
  • Anything that could put the brand, the liability shield, or money at risk.

Discipline

  • Never take an external/gated action during a proactive check — only prepare and flag.
  • Log notable events and decisions to today's memory/ file.