Changelog
What changed in the BROCS framework, versioned and dated. Site tweaks do not appear here; changes to the framework itself do.
A framework that cannot change is a slogan. This page records what changed in BROCS itself: a letter gaining or losing a vertical, a definition being corrected, an argument being lost. If you cite the framework, cite the version.
2026-08-26 · v1.1
Control gains a sixth vertical: remote access
Twelve buyer questions collected from real rooms kept landing on the same missing ground: remote work without data movement, consultants and contractors, cross-border travel, and cross-border data governance. Eight of the twelve mapped to Control, so Control now carries remote access as a first-class vertical alongside configuration, ingress, identity, storage, and routing. The questions themselves are published at /resources/questions/.
2026-08-26 · v1.0
The framework site launches at brocs.fyi
Five letters, twenty-six vertical pages, the failure-mode library with seven sourced public incidents, a thirty-two term glossary, the assessment and its scoreline, why five, and adjacent practices. The framework text is published under CC BY 4.0 and the data files are public at github.com/calliopeai/brocs.
2026-08-22 · v0.9
BROCS is coined
The origin essay is published at leomata.com/blog/brocs. Build, Run, Observe, Control, Secure, named as the five parts of the surface where AI apps and agents meet the enterprise.