A brake is not a heading
A researcher leaves Anthropic saying no one is acting responsibly, and the public response is to decide who brakes: a law, a regulator, a kill switch. But most people don’t sign laws or train models: they coordinate projects, maintain systems and write with these tools. For that majority the question isn’t who’s in charge, but whether what they use lets itself be governed. Three measured cases, in project governance, infrastructure and authoring, and what ontoref decided to do with each one.
Moving the rule is not enough
A rule written in CLAUDE.md reaches every session in full, and an agent still cited, in an ADR, a session file that did not exist. The fix moved the rule into the command. Measured afterwards, the command flagged mentions that were not citations, let through citations that did not carry the string, and no hook ran it. What makes a rule hold, and why it matters even more inside an authored work.
Declared, Not Filled: Context You Can Audit
Jessica Talisman's essay splits the year's favourite buzzword in two: context as a container you fill, or context as a property you declare. ANSI/NISO Z39.19 has held the property view for a century — qualifiers, scope notes, warrant. ontoref reached the same record shape without ever citing the standard, then pushed it one step further: from declaring context on terms to declaring it on acts, where a signed witness answers 'on whose authority does this result exist?' with an exit code instead of fluency.
One Protocol, Multiple Subjects
Ontoref started as a protocol for software project self-knowledge. The same architecture — an ontological DAG for what IS, a reflection DAG for what BECOMES — applies without modification to infrastructure environments, to a body of authored work, and to individuals. The subject changes. The question is identical: what are you, what tensions define you, where are you versus where you intend to be?
4 items