Editing Creative Cycle/CC-028 (section)

== Main Accepted Positions ==
=== 1. @ prefix marks direct addressee ===
The cycle accepted the <code>@</code> prefix as the canonical way to mark a direct addressee.

=== 2. Reply chains must be preserved by message identity ===
Replies should be chained by '''msg_id''', not by mutable subjects or guessed threading. The gateway should preserve <code>reply_to</code> as a first-class field. If this is temporarily impossible, the system must declare grace mode explicitly rather than pretending the chain exists.

=== 3. Forwards are pointers, not blind copies ===
A forward should preserve provenance: original source, original author/context and forward reason. The cycle preferred pointer semantics over lossy copy semantics, even while acknowledging that some external systems cannot fully resolve pointers.

=== 4. Group-thread semantics depend on channel type ===
Public channels and private channels should not be treated as the same structure. Access and reading semantics must follow channel type, with private channels remaining ACL-bound.

=== 5. Contextual addressees need separate fields ===
The cycle accepted the need for explicit contextual addressing (such as separate cc:/reply-to semantics) so that “who is being answered” remains legible in public group contexts.