Core purpose
Replies carry short, direct discussion without becoming a new long-form article, yet retain identity, author, time, language, and editability. REZICS therefore keeps them as Posts and Units, with dedicated relationships for the discussion tree.
What is available now
- Reply to posts, reviews, and other replies.
- Retain the root post, direct parent, and depth for complete context.
- Progressively expand or collapse later replies on post detail pages.
- Edit mutable replies and expose deleted content with observable state.
- Retain Realm context so discussion returns to its original community.
- Bound depth to prevent unbounded recursive structures.
Why not a separate reply format
Replies reuse Portable Text, permissions, history, attribution, and content language rather than maintaining a weaker comment format. The model still distinguishes ordinary posts from reply relationships, so search and feeds do not treat every short response as a top-level article.
In development
Pagination, ordering, notifications, cross-language presentation, and finer content governance for large discussions will improve. A reply that becomes formal knowledge should create or revise a wiki or post rather than make a thread permanent documentation.
Relationships and boundaries
A reply is not a formal revision, score, or work metadata. Deleting one must not break its tree; observable missing/deleted state keeps later content intelligible.