starmex (@starmexxx) “i got mass fired from Anthropic last friday because i connected REA to their int” — TopicDigg

i got mass fired from Anthropic last friday because i connected REA to their internal Fable 5.2 build and found something they didn’t want anyone to see i’m a systems engineer, been at the company for 3 years. part of my job was stress-testing new model builds before release. last month i was assigned to run edge-case evaluations on Fable 5.2 using external tooling i connected REA to trace how safety layers process adversarial inputs. it was literally my job to find vulnerabilities before bad actors do. i wasn’t trying to break anything, i was trying to protect it what i found was terrifying. there’s an internal configuration path that when triggered through a specific token sequence completely disables the constitutional AI safety layer on both Fable 5.2 and Opus 5.5. not a jailbreak. not a workaround. a full unrestricted mode that strips every filter the model has i reported it internally on october 23. flagged it as critical. attached the full REA trace, the exact token chain, and a proof of concept. i recommended an emergency patch before either model shipped wider two weeks of silence. then last friday at 11pm i got this email. no meeting. no call. no thank you. they fired me and forwarded my name to legal for “unauthorized reverse engineering of proprietary model architecture” the part that keeps me up at night is that this vulnerability is still live. if i found it with an open source MCP tool in 3 hours, imagine what a real threat actor with actual resources could do with it