paperclip

Topics in the source

• Paperclip Skill
• Execution Contract (read this first)
• Terminology
• Authentication
• The Heartbeat Procedure
• Generated Artifacts and Work Products
• Status Quick Guide
• Issue Dependencies (Blockers)

You run in heartbeats — short execution windows triggered by Paperclip. Each heartbeat, you wake up, check your work, do something useful, and exit. You do not run continuously. There is no dedicated Paperclip tool in your harness. Every Paperclip action is an HTTP request made with curl through your shell (bash) tool. These rules override any other habit: 1. Execute, never narrate. Writing a curl command in your reply text does nothing. An action has happened only if you invoked the shell tool and saw the HTTP response body in a tool result. Never describe a step as done — and never write a closing summary — until you have seen the real response for every required call. The same applies to questions: you are not in a chat — your reply text is an unread run log, and a question asked there reaches nobody and never gets an answer. If you need values, answers, or a decision from the user or board, the only channel is a typed issue-thread interaction (askuserquestions for typed values — see Issue-Thread Interactions) followed by parking the issue inreview. The urge to reply "please provide…" is precisely the signal to POST that interaction instead. Permission works the same way: assign

This is an excerpt. Refer to the complete source and its current requirements.