It's a bit more complicated on a decentralized platform.

1) There needs to be a base K01-note and reply K01-notes, that are all published at once.

2) The reply notes need to stay in a specific order or be numbered (1/5), otherwise it gets confusing because clients reorder notes and there's no clear way to tell which note came first, except maybe timestamp.

3) they need to be identifiable as a cohesive thread, so that a change from thread-view to article-view doesn't accidentally pick up more replies from the same author in the same thread.

This could all just be done with a tag, or some standard keyword in the content that clients could choose to interpret or ignore.

Long-form threads would probably require an index. Be too messy, otherwise.