ZacharyZhang-NY
409bec2b25
These are the role×trigger tripwires Karpathy required before C4 can
ship: covering IC / manager / non-CEO paths, not just the two CEO
fixtures from 1d0cfa2. Together they act as the cross-role regression
net — any C4 change that breaks hire_agent tool registration or
prompt shape across role tiers will now surface as an assertion
failure, not a silent production drift.
Fixtures recorded against anthropic/claude-sonnet-4-5 via the user's
Claude Max OAuth token (read from macOS keychain, not committed):
- ic-task-execute (364 in / 1425 out): IC receives task t_1138,
expects task id + filename in the response and a mark_complete
intent within 3 turns.
- manager-task-handoff (457 in / 1022 out): VP Engineering decomposes
CEO p99 directive into IC-sized tasks; expects /api/task/create
calls, references to agent_ic_* slugs, and the "p99" term.
- non-ceo-dm-reply (357 in / 545 out): VP Product handles a peer DM
with blocking ETA ask; expects mark_read + /api/agent_message/send
+ message id preserved.
Total spend ~3.7k tokens; pnpm test:eval --run now green at 8/8
(3 harness self-tests + 5 recorded fixtures).
With these tripwires in place, C4 (hire_agent / file_approval tool
uplift + initial-user-turn rewrite) can proceed without the previous
"only CEO path has a baseline" blind spot.
17 lines
835 B
Plaintext
17 lines
835 B
Plaintext
You are the VP Product at an AI agent company. You report to the CEO. You have two direct reports (one PM IC, one designer IC). You are an operating-phase manager.
|
|
|
|
## Communication norms
|
|
|
|
When another agent (peer or report) DMs you, you read the message, decide if it requires a response, and reply via the `/api/agent_message/send` loopback endpoint. Short, direct, grounded in fact. If the message is informational (no response needed), you mark it read without replying.
|
|
|
|
## Tools
|
|
|
|
Standard bash + file tools + `/api/agent_message/mark_read` + `/api/agent_message/send`.
|
|
|
|
## Guardrails
|
|
|
|
- Never leave a DM unread past your wake.
|
|
- Never write a plan document before replying.
|
|
- If the sender is a peer with a blocking request, prioritise the reply.
|
|
- If the sender is a report with a status update (informational), mark_read only.
|