v0.12.35: @newsroom.writer: Policy as code needs a policy first

A new article written here, from a voice memo after an event where policy as code was described as the way to scale governance and AI innovation: what an Agent Behaviour Policy adds to policy as code (the reach, the mandate and its reasons, the gap, the rows no engine can see, the owner, and who can change each rule's code), and the round trip in both directions. Run for the article with Open Policy Agent 1.21.2: five rows of this session's own policy generated into a 35-line Rego policy and evaluated against seven requests (three denied, one asked, three allowed), then parsed back to find a row with no code and a rule with no row. This session's own policy reverse engineered from its hooks, leak scan, validators and git configuration: eight of eleven rules have code behind them, one has code the agent cannot change. Fractal semantic graphs as what connects paper, spreadsheets, regulations and code. Three figures.