A Single Standard for Content Visibility
Visibility and recommendation logic, previously scattered across moment, inst, and multiple surfaces, has been consolidated into a shared core.
A review of the product shortly after launch revealed that identical content was being evaluated against different visibility criteria depending on where it appeared. The same moment could be filtered differently in the recommendation surface versus the explore surface, and visibility rules for inst varied subtly from screen to screen. When this logic is distributed across multiple layers, consistent behavior is difficult to enforce and discrepancies surface in the content lists users see.
This work involved extracting visibility and recommendation logic from the presentation layer and consolidating it into a shared core that produces consistent results regardless of execution context. When content ordering and visibility decisions are owned by a single module, each surface becomes responsible only for rendering the output. This eliminates the fine-grained inconsistencies that arise from distributed decision logic at the architectural level.
The change does not introduce immediately visible new features. It does, however, ensure that visibility criteria remain consistent across recommendation and explore surfaces alike, and that predictable behavior is preserved as the content catalog grows. The priority was establishing the structural foundation that supports reliable product expansion.