Comments
One ordinary comment shape can serve a proposal discussion and a Chat reply. The caller supplies meaning and content. Live Wires supplies the shared presentation hooks.
The first example in each pair reproduces the current consumer structure from its inspected template. The second uses the shared hooks with the same content for a direct visual comparison.
Proposal comment — current source visual reference
I support the proposal. The repair schedule gives the crew a clear first step, and the budget keeps the work inside the amount we agreed to spend.
Same proposal comment — shared hooks
Chat reply — current source visual reference
I can take the first shift on Tuesday. I’ll post the supply list here before the end of the day.
Same Chat reply — shared hooks
Unlinked author and no avatar
The author has no profile link or avatar. The comment still has a stable anchor and a semantic time.
Unlinked author and avatar
The avatar is decorative and unlinked. The visible author name identifies the person.
Long names, timestamps, links, and code
Use this long reference link to check wrapping. Inline code can contain a long identifier such as proposal_response_history_entry_identifier_2026_09_30.
proposal_id = "north-workshop-repair-plan"
decision_reference = "recorded-after-the-meeting-and-linked-from-the-minutes"Rich body, edited metadata, and caller actions
The crew shared the revised schedule and annotated the damaged stair:
- Replace the cracked tread.
- Photograph the finished repair for the maintenance record.
Keep the project notes at the maintenance record.
repair.status = "complete"
repair.reviewed_by = "the next shift"Edited
Inherit an enclosing scheme
The comment sets no background or text color. It inherits the surrounding scheme.
I support the proposal. The repair schedule gives the crew a clear first step, and the budget keeps the work inside the amount we agreed to spend.