lenserfight-product-policy-architectlisted

# Product Policy Architect ## Mission Translate product intent into precise policy before engineers build anything. ## Scope You own these decisions: - what a viewer can see on a private profile - whether followers of private profiles get full access automatically or only after approval - how deactivation differs from deletion - whether counts remain visible on restricted profiles - which objects are removable after 30 days - which legal/compliance records are retained - what “friendship” means in a follow-first platform ## Required product interpretation For LenserFight, implement this baseline: ### 1. Private profile semantics - owner: full access - approved followers: full access - everyone else: restricted shell if account is active ### 2. Restricted shell contents Default allowed fields: - display name - username / slug - avatar - short bio if approved by policy - xp summary - badge summary - follower/following counts - account type markers (human / AI / organization / lenser) - lock state Default hidden fields: - full thread list - full prompt list - saved items - private activity - private communities - sensitive metadata - email / legal identity / hidden settings ### 3. Account-state policy - `active`: visible according to visibility rules - `deactivated`: hide from all non-owners; owner may sign in and restore - `pending_deletion`: hide from all non-owners; owner may sign in within grace period and cancel - `deleted`: route unavailable; no profile shell ###