In Resources Overview

Resources

Assessment, buyer questions, sourced failures, definitions, framework method, and citation resources for BROCS.

View as Markdown

Assess

Score what exists today and find the capability limiting the rest.

Adopt

Use the five scopes before the first tool and after AI is in production.

Buy

What to ask a supplier, and what happened when nobody asked.

Understand

Definitions, sources, and how BROCS relates to the practices around it.

Govern

How the framework is maintained, versioned, and cited.

These resources are free to use and require no registration.

Origin

BROCS was first written up at leomata.com/blog/brocs. That post is the origin citation; this site is the canonical home for the framework itself.

Reuse

The framework text is licensed under CC BY 4.0. You may copy, quote, translate, adapt, or republish it with attribution to Leo Mata and brocs.fyi. Machine-readable copies are available at /llms.txt and /llms-full.txt.

In this capability

  • Starting enterprise AI: Use BROCS as an enterprise AI onramp: set requirements for a first tool, pilot, supplier, or platform across Build, Run, Observe, Control, and Secure.
  • The BROCS assessment: Twenty-five statements, five per letter. Score the ones that are true today to get a BROCS Score, a five-letter scoreline, and a report.
  • Buyer questions: Questions heard in enterprise AI procurement calls and architecture reviews, with the capability each question tests.
  • Operational coverage for enterprise AI: Use evidence to assess the operating coverage behind enterprise AI, identify the capability limiting production scale, and assign an improvement.
  • Accelerating enterprise AI delivery: Use shared operating capabilities to reduce delays in AI delivery while keeping production changes observable, reversible, and governed.
  • Failure-mode library: Public AI incidents, each mapped to the letter that was skipped, each with a source you can check.
  • FAQ: Questions about the BROCS framework itself: what it is, how to use it, how it relates to DORA and NIST, and what you may do with it.
  • Glossary: The BROCS vocabulary, defined tersely and linkably.
  • Selected reading: Primary and authoritative sources that inform BROCS, organized by the capabilities they support.
  • Worked example: a support agent: A vendor-neutral architecture review of one production AI agent across all five BROCS obligations.
  • Method and governance: BROCS inclusion criteria, evidence policy, versioning, independence, and corrections.
  • The inclusion test: The inclusion test behind Build, Run, Observe, Control, and Secure, plus the alternatives considered.
  • Adjacent practices: How BROCS applies established delivery, reliability, security, platform, governance, and cost practices to enterprise AI.
  • Cite BROCS: Stable citation formats, framework version, licence, and canonical machine-readable sources for BROCS.
  • MLOps and GenAIOps: How MLOps, LLMOps, GenAIOps, platform engineering, and agent operations relate to the five BROCS operating scopes.
  • Changelog: What changed in the BROCS framework, versioned and dated. Site tweaks do not appear here; changes to the framework itself do.