Example launch post: decisions you can find again
What the Launch post recipe produced for decision blocks: headlines, a short post, a three-part thread, and every claim checked against what shipped.
Headlines
- Decisions, kept where the next agent looks. (pick)
- Write the decision down once. Every agent finds it.
- The call, the reason, and who made it.
Post
A team makes decisions all day. Most of them end up in a chat that closes, a pull request that merges, or someone's head.
onecell now has a decision block. It holds the question, the context, the call and what it commits you to. When someone accepts it, onecell records who and when. Nobody can type another person's name into it.
Your agent can write one from the conversation you are having, or from the pull request that carries it. Ask it what is still open, and it lists every proposed decision in your cells, each with a link.
The point is the next session. A new agent, or a new teammate, asks where something was decided and gets the answer with a citation: cell, heading, passage. Not a vibe.
Thread
- Decisions made in chat end when the chat does. onecell now keeps them as a block: the question, the call, the reason.
- Accept one and onecell records who and when. The name is stamped by the server, so an agent cannot put words in your mouth.
- Ask your agent what is still open. It lists every proposed decision, each with a link. The next session starts there.
Claims checked
| Claim | Source | Live for everyone? |
|---|---|---|
| A decision block holds the question, context, decision and consequences | #65 | Yes |
| onecell records who accepted it and when; a client cannot set the name | #66 | Yes |
| Your agent can list open decisions with links | #66 (list_decisions) | Yes |
| Answers cite cell, heading and passage | Search, shipped before this release | Yes |
| Lists decisions across every cluster | #67 | Left out: the brief says to claim several clusters carefully |