The ticket standard for cards
The one shape every card an agent files for a person follows, how agents are held to it, and how the board shows a card that falls short.
When an agent files a card for a person, it writes it in one shape, so every ticket reads the same whichever agent wrote it:
- A title under 70 characters
- Then these sections, in this order, each as a
##heading:- User story
- Context
- Success criteria
- Definition of done
- Todo
- Out of scope
How it is enforced
- In Belai. Before an agent’s tool writes the card, Belai checks it and sends the gaps back to the agent, which fixes them first.
- On the server. The factory checks every card the same way, from the same shared rules, so the two can never disagree.
The server never refuses a card for falling short: a host’s board sync must never stall on one card. The board shows what is missing instead.
Templates whose agents write tickets say so on the Templates page. The sf:ticket label asks for a card to be written in the standard from an issue.