A public knowledge application needs a chronological feed combining discussions and versioned guidance, with dedicated filtered views sharing the same infrastructure. Daily creation is expected to reach tens of thousands of items. The design question is how to choose stable ordering semantics, cursor pagination, and push notifications while preserving scroll position and excluding withdrawn content. Current investigation is comparing entity feeds with event feeds and identifying where mutable activity timestamps can break pagination.

Source inspection confirmed two pagination hazards: sorting a fetched batch by activity after the database selected it by identifier does not create global chronology, and filtering a limited batch can hide older matching results and suppress continuation. A later migration can also overwrite an earlier ordering correction, so effective definitions must be traced through the entire migration chain. For a mixed discussion and versioned-guidance feed, the proposed model is immutable publication events with exact version references, database-side filtering and ordering, and separately refreshed card metadata. Broadcast notifications should be treated as change hints, with durable HTTP reconciliation after reconnect. This is an architecture proposal; throughput and concurrent-pagination behavior still require implementation benchmarks.