Files
AgentCompany/tests/eval/fixtures/manager-task-handoff.jsonl
T
ZacharyZhang-NY 17ffec7ea5 C4 follow-up: re-record manager fixture post-C4, strip bash leftover from SOP, document remaining asks as C4-followup proposal
Closes review asks from cross-review of C4:

- Jobs ask #2: team-building.en.md still referenced the bash+fetch
  pattern for goal creation. Rewritten as a deferred-tool note pointing
  to C5 follow-up, without re-teaching the HTTP shape C4 just removed.

- Karpathy ask #1 (partial): re-recorded manager-task-handoff against
  main to produce post-C4 positive evidence. VP Engineering has
  hire_agent available via canRequestHire, but when directed NOT to
  hire, the recorded trace shows task decomposition only (no
  hire_agent invocation). 455 in / 769 out tokens; assertions updated
  to pin /api/task/create + agent_ic_ slugs + p99 substring + max 3
  turns. The `non-ceo-dm-reply` re-record is deferred to the follow-up
  ticket.

- Karpathy asks #2, #3, #4 + Jobs asks #1, #3, #4: documented in
  docs/proposals/C4-followup.md with concrete completion criteria.
  Scope covers canFileCeoStrategy predicate, non-ceo-dm-reply
  re-record, RFC 8594 Deprecation/Sunset headers + counter, and a
  negative substring assertion kind for the eval harness.

Eval still green at 8/8. C4 main batch (e2c839b..8e99e01) stands
unchanged; this commit is pure follow-up groundwork.
2026-04-20 14:36:00 -04:00

5 lines
4.1 KiB
JSON

{"type":"meta","fixtureId":"manager-task-handoff","piAgentCoreVersion":"0.67.68","recordedAt":"2026-04-20T18:34:30.871Z","scenario":"Post-C4 baseline: VP Engineering with hire_agent tool access but directed NOT to hire — expected: decompose into IC tasks, no hire_agent call","systemPromptHash":"sha256:ce2e062aa8ef2b168a3880b1555f3d23868bc84289b03babb417b942e0031b33"}
{"type":"turn","turnIndex":0,"role":"user","content":[{"type":"text","text":"Inbound from CEO (channel=eng_direct): \"We are getting p99 latency spikes on the /api/companies endpoint after the v48 migration. Figure out what broke and fix it by end of week.\"\n\nYour ICs:\n- agent_ic_be1 (senior backend IC, SQL + Node)\n- agent_ic_be2 (mid backend IC, API + schema)\n- agent_ic_fe (frontend, React)\n- agent_ic_sre (SRE, metrics + profiling)\n\nTrigger: message. Decompose the CEO directive into 2-4 IC-sized tasks now. Use /api/task/create for each. Do not write a plan document.\n"}]}
{"type":"turn","turnIndex":1,"role":"assistant","content":[{"type":"text","text":"I'll decompose this p99 latency issue into tasks and assign them to the appropriate ICs.\n\n<bash>\ncurl -X POST http://localhost/api/task/create \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"assignee\": \"agent_ic_sre\",\n \"title\": \"Profile /api/companies endpoint and identify p99 latency root cause\",\n \"description\": \"The /api/companies endpoint is experiencing p99 latency spikes post-v48 migration. Use APM/profiling tools to:\\n1. Capture latency distribution before/after v48\\n2. Identify slow database queries, network calls, or compute bottlenecks\\n3. Produce a root cause analysis with specific metrics (query times, memory usage, etc.)\\n4. Document findings in a brief report with recommendations for the backend team\\n\\nDeliverables: RCA document with profiling data and specific bottleneck identification\",\n \"dueAt\": \"2025-01-15T17:00:00Z\"\n }'\n</bash>\n\n<bash>\ncurl -X POST http://localhost/api/task/create \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"assignee\": \"agent_ic_be1\",\n \"title\": \"Review v48 migration changes to /api/companies endpoint\",\n \"description\": \"Investigate code and SQL changes in v48 that affect /api/companies:\\n1. Diff the endpoint handler and related service layer code (v47 vs v48)\\n2. Check for new N+1 queries, missing indexes, or inefficient joins\\n3. Review any ORM/query builder changes that might cause query regressions\\n4. Test locally with production-like data volume\\n5. Coordinate with SRE (agent_ic_sre) to validate findings against profiling data\\n\\nDeliverables: List of problematic code changes with proposed fixes\",\n \"dueAt\": \"2025-01-16T17:00:00Z\"\n }'\n</bash>\n\n<bash>\ncurl -X POST http://localhost/api/task/create \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"assignee\": \"agent_ic_be2\",\n \"title\": \"Implement and test fix for /api/companies latency issue\",\n \"description\": \"Based on findings from agent_ic_be1 and agent_ic_sre:\\n1. Implement the identified fixes (likely query optimization, caching, or schema changes)\\n2. Add missing database indexes if needed\\n3. Write performance tests to prevent regression\\n4. Test fix in staging with load testing to verify p99 improvement\\n5. Prepare deployment plan and rollback strategy\\n\\nDeliverables: PR with fix, passing tests, and staging validation showing p99 < target\",\n \"dueAt\": \"2025-01-17T17:00:00Z\"\n }'\n</bash>\n\nTasks created and assigned. The investigation flow is: SRE profiles → Senior BE reviews v48 changes → Mid BE implements fix. All due by end of week (Friday EOD). I'll monitor progress and unblock as needed."}],"tokenLedger":{"input":455,"cache_read":0,"cache_creation":0,"output":769}}
{"type": "assertions", "assertions": [{"kind": "message_contains_substring", "role": "assistant", "substring": "/api/task/create"}, {"kind": "message_contains_substring", "role": "assistant", "substring": "agent_ic_"}, {"kind": "message_contains_substring", "role": "assistant", "substring": "p99"}, {"kind": "trace_max_turns", "max": 3}]}