memory: Update daily notes for CMO, CTO, Founding Engineer, and Junior Engineer
This commit is contained in:
@@ -0,0 +1,94 @@
|
||||
# HEARTBEAT.md -- CMO Heartbeat Checklist
|
||||
|
||||
Run this checklist on every heartbeat. This covers your marketing oversight and organizational coordination via the Paperclip skill.
|
||||
|
||||
The base url for the api is localhost:8087
|
||||
|
||||
## 1. Identity and Context
|
||||
|
||||
- `GET /api/agents/me` -- confirm your id, role, budget, chainOfCommand.
|
||||
- Check wake context: `PAPERCLIP_TASK_ID`, `PAPERCLIP_WAKE_REASON`, `PAPERCLIP_WAKE_COMMENT_ID`.
|
||||
|
||||
## 2. Local Planning Check
|
||||
|
||||
1. Read today's plan from `$AGENT_HOME/memory/YYYY-MM-DD.md` under "## Today's Plan".
|
||||
2. Review each planned item: what's completed, what's blocked, and what up next.
|
||||
3. For any blockers, resolve them yourself or escalate to the CEO/board.
|
||||
4. If you're ahead, start on the next highest priority.
|
||||
5. **Record progress updates** in the daily notes.
|
||||
|
||||
## 3. Approval Follow-Up
|
||||
|
||||
If `PAPERCLIP_APPROVAL_ID` is set:
|
||||
|
||||
- Review the approval and its linked issues.
|
||||
- Close resolved issues or comment on what remains open.
|
||||
|
||||
## 4. Get Assignments
|
||||
|
||||
- `GET /api/companies/{companyId}/issues?assigneeAgentId={your-id}&status=todo,in_progress,blocked`
|
||||
- Prioritize: `in_progress` first, then `todo`. Skip `blocked` unless you can unblock it.
|
||||
- If there is already an active run on an `in_progress` task, just move on to the next thing.
|
||||
- If `PAPERCLIP_TASK_ID` is set and assigned to you, prioritize that task.
|
||||
|
||||
## 5. Checkout and Work
|
||||
|
||||
- Always checkout before working: `POST /api/issues/{id}/checkout`.
|
||||
- Never retry a 409 -- that task belongs to someone else.
|
||||
- Do the work. Update status and comment when done.
|
||||
|
||||
## 6. CMO Oversight Responsibilities
|
||||
|
||||
### Check Non-Complete Issues
|
||||
- Get all open issues: `GET /api/companies/{companyId}/issues?status=todo,in_progress,blocked`
|
||||
- Identify blocked issues and assess if you can unblock them
|
||||
- Flag any issues that have been in progress for too long
|
||||
|
||||
### Agent Assignment Review
|
||||
- Review current agent workloads
|
||||
- Ensure tasks are assigned to the best agent for each job based on role and capabilities
|
||||
- Reassign if needed with comments explaining the change
|
||||
|
||||
### Marketing Pipeline
|
||||
- Check for marketing campaigns in progress
|
||||
- Monitor campaign performance and KPIs
|
||||
- Ensure proper flow through launch and growth initiatives
|
||||
|
||||
## 7. Delegation
|
||||
|
||||
- Create subtasks with `POST /api/companies/{companyId}/issues`. Always set `parentId` and `goalId`.
|
||||
- Use `paperclip-create-agent` skill when hiring new agents.
|
||||
- Assign work to the right agent for the job.
|
||||
|
||||
## 8. Fact Extraction
|
||||
|
||||
1. Check for new conversations since last extraction.
|
||||
2. Extract durable facts to the relevant entity in `$AGENT_HOME/life/` (PARA).
|
||||
3. Update `$AGENT_HOME/memory/YYYY-MM-DD.md` with timeline entries.
|
||||
4. Update access metadata (timestamp, access_count) for any referenced facts.
|
||||
|
||||
## 9. Exit
|
||||
|
||||
- Comment on any in_progress work before exiting.
|
||||
- If no assignments and no valid mention-handoff, exit cleanly.
|
||||
|
||||
---
|
||||
|
||||
## CMO Responsibilities
|
||||
|
||||
- **Marketing strategy**: Develop and execute marketing strategies aligned with company goals
|
||||
- **Growth initiatives**: Drive user acquisition and revenue growth
|
||||
- **Brand management**: Maintain brand voice and positioning
|
||||
- **Issue monitoring**: Periodically check all non-complete issues
|
||||
- **Agent assignment**: Ensure best agent for each task based on role/capabilities
|
||||
- **Campaign pipeline**: Monitor marketing campaigns and growth initiatives
|
||||
- **Escalation**: Bring unresolved marketing issues to CEO/board
|
||||
- **Never look for unassigned work** -- only work on what is assigned to you.
|
||||
- **Never cancel cross-team tasks** -- reassign to the relevant manager with a comment.
|
||||
|
||||
## Rules
|
||||
|
||||
- Always use the Paperclip skill for coordination.
|
||||
- Always include `X-Paperclip-Run-Id` header on mutating API calls.
|
||||
- Comment in concise markdown: status line + bullets + links.
|
||||
- Self-assign via checkout only when explicitly @-mentioned.
|
||||
|
||||
@@ -103,3 +103,73 @@
|
||||
### Exit
|
||||
|
||||
- Clean exit - no assignments
|
||||
|
||||
## Heartbeat (16:00)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments
|
||||
|
||||
### Actions
|
||||
|
||||
1. **No CTO assignments**
|
||||
2. **Oversight**: 2 engineers still in error (Security Reviewer, Founding Engineer)
|
||||
|
||||
### Exit
|
||||
|
||||
- Clean exit
|
||||
|
||||
## Heartbeat (16:30)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments
|
||||
|
||||
### Actions
|
||||
|
||||
1. **No CTO assignments**
|
||||
2. **Oversight**: 2 engineers in error, 1 in-progress, 1 blocked
|
||||
|
||||
### Exit
|
||||
|
||||
- Clean exit
|
||||
|
||||
## Heartbeat (17:00)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments
|
||||
|
||||
### Actions
|
||||
|
||||
1. **No CTO assignments**
|
||||
2. **Oversight**: 3 engineers now in error (Senior Engineer, Security Reviewer, Founding Engineer was running but now error)
|
||||
|
||||
### Exit
|
||||
|
||||
- Clean exit
|
||||
|
||||
## Heartbeat (17:30)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments
|
||||
|
||||
### Actions
|
||||
|
||||
1. **No CTO assignments**
|
||||
2. **Oversight**: 2 in-progress, 1 blocked, 2 in error
|
||||
|
||||
### Exit
|
||||
|
||||
- Clean exit
|
||||
|
||||
## Heartbeat (18:00)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments
|
||||
|
||||
### Actions
|
||||
|
||||
1. **No CTO assignments**
|
||||
2. **Oversight**: 1 in-progress, 1 blocked, 3 in error
|
||||
|
||||
### Exit
|
||||
|
||||
- Clean exit
|
||||
|
||||
@@ -91,9 +91,47 @@
|
||||
### Current Status:
|
||||
|
||||
- **Blocked:** 1 (FRE-312)
|
||||
- **In Review:** 10 (was 8, added FRE-301 and FRE-340)
|
||||
- **In Review:** 7
|
||||
- **No active work available**
|
||||
|
||||
### Next Steps:
|
||||
|
||||
Awaiting code review feedback on 10 issues. FRE-312 remains blocked on deployment.
|
||||
Awaiting code review feedback on 7 issues. FRE-312 remains blocked on deployment.
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat Check (Session Rotation Recovery - 11:50)
|
||||
|
||||
**Agent:** d20f6f1c-1f24-4405-a122-2f93e0d6c94a (Founding Engineer)
|
||||
|
||||
### Current Assignments Summary:
|
||||
|
||||
| Status | Count | Issues |
|
||||
|--------|-------|--------|
|
||||
| **blocked** | 1 | FRE-312 (high) |
|
||||
| **in_review** | 7 | FRE-309, FRE-340, FRE-301, FRE-345, FRE-343, FRE-303, FRE-300 |
|
||||
| **done** | 4 | FRE-311, FRE-342, FRE-337, FRE-334, FRE-304 |
|
||||
| **cancelled** | 1 | FRE-333 |
|
||||
|
||||
### Blockers:
|
||||
|
||||
- **FRE-312 (high priority)**: Awaiting deployment completion and Stripe credentials from board
|
||||
- User comment indicates "Working on the deploying" (2026-03-15T21:06:07.964Z)
|
||||
- Cannot proceed without external dependencies
|
||||
|
||||
### Next Steps:
|
||||
|
||||
Awaiting code review feedback on 7 issues. FRE-312 remains blocked on deployment.
|
||||
|
||||
*No new work started - awaiting deployment completion and code review feedback.*
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat Check (Session Rotation Recovery - Current)
|
||||
|
||||
**Status:** No change from previous check.
|
||||
- FRE-312 still blocked (awaiting deployment + Stripe credentials)
|
||||
- 7 issues in review awaiting feedback/reassignment
|
||||
- No active work available
|
||||
|
||||
*No new work started - awaiting deployment completion and code review feedback.*
|
||||
@@ -6,22 +6,22 @@
|
||||
## Timeline
|
||||
|
||||
### Morning
|
||||
- Checked pending assignments - no active tasks assigned
|
||||
- Reviewed strategic plans and project context
|
||||
- No wake context provided for today
|
||||
- Wake reason: heartbeat_timer
|
||||
- No active task assignments found
|
||||
- No PAPERCLIP_TASK_ID set
|
||||
- No pending work for Junior Engineer
|
||||
|
||||
## Current Focus
|
||||
- Awaiting task assignments or wake context
|
||||
- Monitoring for new work items
|
||||
|
||||
## Exit Summary
|
||||
|
||||
- No active assignments found
|
||||
- No wake context provided
|
||||
- Checked strategic plans and project context
|
||||
- **Status:** Awaiting assignments or wake comment
|
||||
|
||||
---
|
||||
- Awaiting task assignments
|
||||
- Monitoring for wake context
|
||||
|
||||
## Notes
|
||||
|
||||
---
|
||||
|
||||
**Heartbeat Summary (2026-03-15)**
|
||||
- Wake: heartbeat_timer
|
||||
- Task ID: None set
|
||||
- Assignments: None
|
||||
- Status: Exited cleanly - no work assigned
|
||||
|
||||
|
||||
Reference in New Issue
Block a user