Read Goal Conversation

The event a goal is pinned to, resolved into what a client draws.

Additive and optional: a goal that anchors nowhere — most of them — carries null here and the page looks exactly as it did before this existed.

This is the whole reason the coach never writes a URL. The reply is plain chat text that ships to any channel as-is, so a link in it would be a link the model chose and nothing validated; here the host resolves the id the conversation anchored to and hands over the official name, date, place and site. The surface renders the card, and the coach's words stay words.

website_url points at the organizer's own site rather than an imperfect.co event page: the athlete is being handed the place where they actually register. It resolves server-side, so retargeting it later is one line here and no change to any client.

The goal's picture as one payload, for the two carriers that send it.

The picture draws itself while the conversation runs, so the page needs the factors as data rather than as document text nobody outside cheshire should be parsing. One payload serves both carriers — the accepted turn's stream event and the conversation read's picture — and both derive it from the same accepted document, which is what makes them unable to disagree.

Full state, never a delta. Every payload carries the complete factor list of its document version, anchors first (:func:picture_factors), so a page that reloads and starts from the conversation read draws the identical picture the stream drew. Motion is the consumer's diff between consecutive payloads, keyed on a factor's name; version_id is the gate, so the same version seen twice moves nothing.

factors is the rim's own type exactly, the passthrough posture :class:GoalDetailResponse takes and for the same reason: a mirrored DTO here would be a second contract to keep in step with the document the coach writes. Empty is normal — the picture forms as the conversation does. Serialized, left stays in the brief; each factor also carries demand and span (:func:_served_factor), so every carrier hands a consumer the shared scale the goals compare on and the axis scale the positions live on. Every demand is null while the rim carries no kind (#2967): :meth:of reads that off the rim, and a picture built any other way (a test's, a lab's read of a payload already served) draws as marked.

title and line are the other two things the live page shows forming (wonderland goals.md, "The live page"): the body's first heading (:attr:~cheshire.goals.document.GoalDocument.title) and the rim's line, both rewritten by the coach as it learns the athlete, so they ride the same full-state payload rather than an event of their own (#2782). None while the document carries neither.

candidates are the framings the athlete is choosing between, drawn as option cards under the arc (#2882): the rim's own list in document order, empty until the coach offers any, each carrying its label and tags when the coach wrote a card for it.

events are the race days the goal holds, in the order they run, so the arc can pin each one on its date as the goal forms (#3309): the rim's own list, empty until the coach writes one.