<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/scripts/tests/before-close-queue.bats, branch main</title>
<subtitle>Claude Code skills, rules, and language bundles
</subtitle>
<id>https://git.cjennings.net/rulesets/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/rulesets/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/'/>
<updated>2026-07-20T02:10:34+00:00</updated>
<entry>
<title>feat(protocols): add the "the list" before-close queue and colloquialisms convention</title>
<updated>2026-07-20T02:10:34+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-20T02:10:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=8fd9e39a1ebf6c6513c77dbc6e70eeee85f9ccb8'/>
<id>urn:sha1:8fd9e39a1ebf6c6513c77dbc6e70eeee85f9ccb8</id>
<content type='text'>
Home proposed two linked cross-project norms and Craig approved rolling them out. Both now ship in the template so every project inherits them.

A new "Colloquialisms and Expansions" section in protocols.org maps Craig's shorthand to a defined action the agent applies without asking. Two seed entries: "put X on the list" appends to a session-scoped Before-Close Queue, and "tell &lt;project&gt; &lt;message&gt;" drops the message in that project's inbox via inbox-send. The set is extensible.

The queue lives under a "* Before-Close Queue" heading in the session anchor, so it resets when the anchor is archived at wrap. Anything that must outlive the session stays a todo.org task. wrap-it-up Step 1 gets a sub-step that works the queue oldest-first before the Summary, so any resulting edits ride the wrap commit, with unfinished items surfaced in the valediction rather than dropped.

I settled three design calls. The reference lives in protocols.org rather than a per-project notes.org (home's local reference), since a synced section is what makes it a shared norm. The queue lives in the session anchor, as home did. The wrap step sits at the front of Step 1 rather than a new half-step, which keeps the "Steps 1 through 5" framing intact. A documentation-integrity bats guards the wiring and the before-the-Summary ordering against a future edit or sync dropping it.
</content>
</entry>
</feed>
