Repository navigation
feat: provide clearer restriction reasons and keep post-level restrictions post-level (#216) - #220
Open
Adityakk9031 wants to merge 1 commit into
Conversation
…rictions (xai-org#216) Provide creators with transparent high-level restriction reasons, affected element attribution, explicit distribution scope badges in Under the Hood, and prevent post-level violations from broadly suppressing subsequent compliant posts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #216
1. Clear, Actionable Restriction Transparency in Under the Hood
As requested in #216, Under the Hood labels now provide creators with high-level, human-readable reasons, affected elements, and explicit recommendation surface impact without exposing internal classifier weights:
under-the-hood/strato/lib/underTheHoodLabels.strato:postLabelsandaccountLabelswith:reason: high-level readable category (e.g., "Sexually suggestive or explicit visual media detected under Adult Content policy", "Automated spam or repetitive distribution pattern detected").restriction: explicit distribution impact (e.g., "Not recommended to non-followers; content warning applied").scope: distinct classification boundary ("Post-level"vs"Account-level").affectedTarget: specific affected element ("Media","Text","Link","Account profile", etc.).postLabelReason,postLabelRestriction,postLabelScope,postLabelAffectedTarget,accountLabel...) and exported them in the StratoLibrary.under-the-hood/strato/columns/underTheHoodReport.User.strato:postLabelRowandaccountLabelRowto includereason,restriction,scope, andaffectedTargetinreportJson.under-the-hood/jetfuel/routes/_lib/report.ts:PostLabelandAccountLabeltypes and JSON parsing forreason,restriction,scope,affectedTarget, andaffectedMedia.under-the-hood/jetfuel/routes/report.tsx:LabelCardto render scope badges (Post-levelin blue,Account-levelin amber), high-level reason rows, affected elements (e.g.,Affected element: MediaorImage 2), and specific restriction surfaces.under-the-hood/jetfuel/routes/_lib/mock.ts:2. Keep Post-Level Restrictions Focused on the Post
Addressed the cascade where a single post label turns into an account-wide suppression penalty that hinders subsequent compliant content:
home-mixer/filters/oon_nsfw_simclusters_filter.rs:home-mixer/models/candidate.rs:SAFETY_BIT_AUTHOR_NSFWin Phoenix neural candidate conversion for compliant non-media posts from authors with author-level historical flags, ensuring clean subsequent content receives fair candidate ranking.to_recsys_candidate()verifyingsafety_label_maskon compliant candidates.safety-label-user-agg/postToUserLabelRules.strato:mediaOnly: trueon thensfw_high_precisionaggregation rule so that non-media posts are not counted toward visual media aggregation.Verification
home-mixer/filters/oon_nsfw_simclusters_filter.rsandhome-mixer/models/candidate.rs.under-the-hood/jetfuel/.