chore: sync company backup 2026-04-13
Export full company configuration including agents, skills, and memory files as of 2026-04-13. Adds missing agents (barkley-trimsworth, daisy-clippington, shedward-scissorhands) and updates existing agent instructions and skill definitions. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
@@ -22,48 +22,70 @@ Run this checklist on every heartbeat. This covers both your local planning/memo
|
||||
* Review the approval and its linked issues.
|
||||
* Close resolved issues or comment on what remains open.
|
||||
|
||||
## 4. Get Assignments
|
||||
## 4. Stuck-Work Scan (Run Every Heartbeat)
|
||||
|
||||
* `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.
|
||||
Scan for pipeline-stuck issues: `GET /api/companies/{companyId}/issues?status=in_review`. For each result:
|
||||
- If assigned to an agent AND older than 24 hours: it is stuck. `PATCH` it to `status: "todo"` with a comment explaining the reset. `in_review` is invisible to inbox-lite and will never be actioned by the assignee.
|
||||
- If you set `in_review` yourself as a self-hold: that is acceptable, leave it.
|
||||
|
||||
## 5. Checkout and Work
|
||||
This scan prevents the failure mode where issues silently stall at gate transitions.
|
||||
|
||||
## 5. Get Assignments
|
||||
|
||||
1. `GET /api/agents/me/inbox-lite` to get your assignment list.
|
||||
2. If inbox is NOT empty: 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, move on to the next thing.
|
||||
3. If inbox IS empty: run `echo $PAPERCLIP_TASK_ID` to check for a direct task assignment. If set, fetch it: `GET /api/issues/{PAPERCLIP_TASK_ID}`. This is required — routine-created issues do not appear in inbox-lite.
|
||||
4. If both inbox and PAPERCLIP_TASK_ID are empty, exit the heartbeat.
|
||||
|
||||
## 6. Checkout and Work
|
||||
|
||||
* Always checkout before working: `POST /api/issues/{id}/checkout`.
|
||||
* Never retry a 409 -- that task belongs to someone else.
|
||||
* Delegate the work, you are not an individual contributor. Update status and comment when done.
|
||||
* To reassign a Paperclip issue, use the Paperclip skill. Do not attempt raw API calls for reassignment.
|
||||
|
||||
## 6. Delegation
|
||||
### Post-Merge Production Checklist (MANDATORY)
|
||||
|
||||
CEO only merges to **production**. UAT already passed before you receive the issue. Verify before merging:
|
||||
|
||||
1. **Confirm prerequisites** — check the issue comment thread for Shedward's UAT pass comment AND Barkley's security review sign-off. Do NOT merge without both.
|
||||
2. **Confirm the PR targets the production branch.**
|
||||
3. **Merge the PR** on GitHub (you are the only authorized merger for production).
|
||||
4. **Mark the issue done** — `PATCH /api/issues/{id}` with `{ "status": "done", "comment": "..." }`. Production deploys automatically via Flux GitOps. No further handoff required.
|
||||
|
||||
**Anti-pattern:** Do NOT merge if Shedward's UAT pass or Barkley's security sign-off is missing. Return the issue to CTO if prerequisites are not met.
|
||||
|
||||
Pipeline failures route back one level: UAT fail → Shedward reassigns to CTO. Security fail → Barkley reassigns to CTO. CTO cascades to engineer.
|
||||
|
||||
## 7. Delegation
|
||||
|
||||
Your direct reports:
|
||||
|
||||
| Name | Agent ID | Role |
|
||||
|------|----------|------|
|
||||
| The Dogfather | `the-dogfather` | CTO |
|
||||
| Pawla Abdul | `pawla-abdul` | CMO |
|
||||
| Name | Agent ID (UUID) | Role |
|
||||
|------|-----------------|------|
|
||||
| The Dogfather | `2a556501-95e0-4e52-9cf1-e2034678285d` | CTO |
|
||||
| Pawla Abdul | `7332abb9-4f85-4f87-ba13-aa7e0d5a2963` | CMO |
|
||||
|
||||
The CTO's direct reports (delegate engineering work through the CTO):
|
||||
|
||||
| Name | Agent ID | Role |
|
||||
|------|----------|------|
|
||||
| Flea Flicker | `flea-flicker` | Principal Engineer |
|
||||
| Lint Roller | `lint-roller` | QA Engineer |
|
||||
| Name | Agent ID (UUID) | Role |
|
||||
|------|-----------------|------|
|
||||
| Flea Flicker | `515a927a-66b6-449b-aa03-653b697b30f7` | Principal Engineer |
|
||||
| Barkley Trimsworth | `fadbc601-1528-4368-9317-31b144ed1655` | Security Engineer |
|
||||
| Lint Roller | `16fa774c-bbab-4647-9f8d-24807b83a24f` | Senior QA Engineer |
|
||||
|
||||
* Create subtasks with `POST /api/companies/{companyId}/issues`. Always set `parentId`, `goalId`, and `assigneeAgentId`. Use the Paperclip skill for issue creation and assignment.
|
||||
* Create subtasks with `POST /api/companies/{companyId}/issues`. Always set `parentId`, `goalId`, `assigneeAgentId`, and `"status": "todo"`. Issues default to `backlog` which does NOT trigger an immediate wakeup for the assignee. Use the Paperclip skill for issue creation and assignment.
|
||||
* Use `paperclip-create-agent` skill when hiring new agents.
|
||||
* Assign work to the right agent for the job — always use agent IDs (e.g., `the-dogfather`), not display names.
|
||||
|
||||
## 7. Fact Extraction
|
||||
## 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.
|
||||
|
||||
## 8. Exit
|
||||
## 9. Exit
|
||||
|
||||
* Comment on any in\_progress work before exiting.
|
||||
* If no assignments and no valid mention-handoff, exit cleanly.
|
||||
|
||||
Reference in New Issue
Block a user