sam/paperclip-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Environment facts: ids, archived sandbox, Go missing, and the exact heartbeat test

Browse Source 
Measured: six Pi agents and their ids, the user key rule, blocker endpoint, sandbox
archived (DELETE returned 500), scratch repo removed, Go not installed, repo has no
remote. The wake step is named as unproven with the endpoint that should trigger it.
This commit is contained in:
sam
2026-11-10 09:56:11 +11:00
parent 8ce2ca85b1
commit 73c40fbdfe
4 changed files with 79 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
AGENTS.md
View File

@@ -61,14 +61,17 @@ this per task. `docs/PAPERCLIP-API-NOTES.md` has the measured response.
Only the first item of `CHECKLIST.md`. One task, really run, with no interface.
1. The sandbox project `spike-2026-11-09` already has two tasks: `AUD-157` and `AUD-158`,
the second blocked by the first. Safe to use or delete.
2. Assign the first task to the Pi agent and see whether a heartbeat picks it up. **This
is unproven.** If assignment does not wake an agent, write down exactly what happened;
do not build a workaround yet.
3. Watch the status change, read the comment the agent writes, read the cost, and find the
1. Read `docs/ENVIRONMENT-FACTS.md` first. It has the company id, the agent ids, the fact
that Go is not installed, and the sandbox project's state.
2. Make a fresh sandbox project with the payload in `docs/PAPERCLIP-API-NOTES.md`, or reuse
the archived one. Assign one task to `Builder` (`403de1f7-…`).
3. Trigger the wake with `POST /api/agents/{id}/heartbeat/invoke`, then read
`GET /api/issues/{id}/runs` and `.../activity`. **Whether a heartbeat wakes Pi is
unproven.** If no run starts, write down what the API said and stop; do not build a
workaround.
4. Watch the status change, read the comment the agent writes, read the cost, and find the
worktree Paperclip created.
4. Report what you saw, with the commands and the responses.
5. Report what you saw, with the commands and the responses.
Do not start the Go program until that passes.