<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/working/question-capture-pattern/proposal-from-archsetup.org, 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-24T05:43:07+00:00</updated>
<entry>
<title>chore(inbox): park the question-capture workflow idea</title>
<updated>2026-07-24T05:43:07+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-24T05:43:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=d3315714d0553f41739ed3ea602b5d42c8113a47'/>
<id>urn:sha1:d3315714d0553f41739ed3ea602b5d42c8113a47</id>
<content type='text'>
Craig's idea, via archsetup: drop a question into the roam inbox, have the agent retrieve it during a pass but hold rather than auto-answer, then answer it live at the next conversation and close on his acknowledgement. The inverse of a VERIFY — the agent owes the answer, not the other way round.

Parked as a spec candidate rather than a direct build: the value is clear, but marking a question item, tracking the answer-owed state, and the new-keyword-vs-VERIFY-variant call are decisions to make with Craig. The proposal is staged under working/.
</content>
</entry>
</feed>
