The lesson
Publish original technical research that first explains how a system is meant to work, then shows how it can be misused, with a diagram for each layer the reader has to keep in mind.
A plain title, 'PolicyHelpers Are a Little Too Helpful', sits over a date and the byline Michael Barclay. 'Introducing PolicyHelpers' explains policy versus settings, then shows a 'Managed policy' diagram tagged 'first populated source wins · no merge' that lists each source in numbered order with its file paths and labels like CLOUD-HOSTED and ADMIN-ONLY. 'The Intended Use Case' describes the legitimate purpose and gives an example managed-settings.json block. 'The Offensive Use Cases' and 'Session Steering' then cover persistence and instruction hierarchy, and list the constraints the author found when testing a named Claude Code version.
Don't copy Origin's Claude Code findings, paths or diagrams. Keep the order of how it works, what it was built for, how it can be abused, with a labeled diagram for each layer and a byline that names the researcher.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.