A Claude Code skill for long agent sessions. A session rarely loses its
purpose in one step: it services a reasonable request, then another prompted
by that, until it is three frames away from what was actually being built.
Swivel declares one core lane per project, logs anything that arrives
from an inbox, tracker or notification as an injected lane, and asks
three questions of every new frame: where did it come from, does it have its
own counterparty and clock, and does the core move if it is done? In-flight
state goes to .swivel/ as stashes built to survive a cold read:
evidenced claims, whose ball each thread is in, the next physical action, and
the landmines.
Published with an audit of its own first three weeks of use: 20 sessions and 9.17 billion input tokens. Its bookkeeping costs 0.35% of input and its stashes read correctly days later. The audit also says plainly that it buys recall, not token savings, and ships a pre-registered experiment to measure that properly. One Markdown file, MIT-licensed.