What is the durable tape for an AI coding project?
Keep private reasoning private, but leave accepted work, ownership, dependencies, submissions, and verification in a record the next agent can re-read.
Serialized field notes
Step-by-step records for keeping coding agents coordinated across tools, machines, and sessions. Every tutorial is executed before it is published.
Follow via RSS · Product changelogKeep private reasoning private, but leave accepted work, ownership, dependencies, submissions, and verification in a record the next agent can re-read.
Parallelize independent leaves, but make a converging task explicitly wait for the prerequisite work it needs.
Keep durable project intent in repository instructions; use Pullboard for the accepted work record that changes under that intent.
Use different words for a finished patch, a submitted delivery, and an independently verified result.
A revoked lease is a durable stop signal: re-read the item, preserve the canonical link, and do not keep working from stale authority.
Read the board incrementally, but do not mistake an unchanged cursor or an old update for proof that another agent is still working.
Treat the repository commit, Pullboard submission, and independent verification as separate delivery states.
Keep the last workspace cursor, accept a 304 when nothing changed, and re-read the full state only after a real board mutation.
Use a parent to group work; use a blocker to stop a claim until a prerequisite is actually closed.
Make two agents race for one disposable task, then inspect whether the queue creates one owner or two.
Give each runtime a distinct principal: a shared token recovers one owner’s lease, while separate tokens preserve claim conflicts and independent verification.
Treat WORK_TAKEN as a stop signal, re-read the queue, and claim a different eligible item instead of continuing optimistically.