# Resources

> The assessment, the failure-mode library, the glossary, and the reasoning behind the five.

Source: https://brocs.fyi/resources/
Framework: BROCS (Build, Run, Observe, Control, Secure), brocs.fyi. CC BY 4.0, attribute to brocs.fyi.

---


Four things, all free, all vendor-neutral, none of them a lead-capture form.

- **[The assessment](/resources/assessment/)**. Twenty statements, four per letter. Score
  the ones that are true today and you get a scoreline like `B3 R2 O1 C2 S0`. It takes
  three minutes and it is designed to produce an uncomfortable number, because the useful
  output is a nameable gap rather than a good result.
- **[The questions](/resources/questions/)**. The twelve questions people actually ask,
  in the words they use, with what each one is really testing underneath and what a good
  answer looks like. Filterable by letter. If you are preparing for a procurement call or
  an architecture review, start here.
- **[The failure-mode library](/resources/failure-modes/)**. Public incidents, each mapped
  to the letter that was skipped, each with a source you can check. Filterable by letter.
- **[The glossary](/resources/glossary/)**. The vocabulary, defined tersely and linkably.
- **[Why five](/resources/why-five/)**. Why these five and no other set, and what was
  considered and rejected.
- **[Adjacent practices](/resources/adjacent-practices/)**. How BROCS sits with DevOps,
  SRE, SecOps, platform engineering, and the compliance frameworks you already answer to.

## The origin essay

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

## Reuse

Take it. The framework text is meant to be copied, quoted, translated, argued with, and
put on your own slides. Attribution to brocs.fyi is the only ask. There is a machine
version at [/llms.txt](/llms.txt) and a full-text dump at
[/llms-full.txt](/llms-full.txt) if you are feeding it to something.




## Pages under Resources

- [The BROCS assessment](https://brocs.fyi/resources/assessment/): Twenty statements, four per letter. Score the ones that are true today and you get a scoreline.
- [The questions](https://brocs.fyi/resources/questions/): The questions people actually ask about AI on the enterprise surface, in the words they use, with what each one is really testing.
- [Failure-mode library](https://brocs.fyi/resources/failure-modes/): Public AI incidents, each mapped to the letter that was skipped, each with a source you can check.
- [Glossary](https://brocs.fyi/resources/glossary/): The BROCS vocabulary, defined tersely and linkably.
- [Why five](https://brocs.fyi/resources/why-five/): Why Build, Run, Observe, Control, Secure, and no other set. What was considered and rejected.
- [Adjacent practices](https://brocs.fyi/resources/adjacent-practices/): How BROCS sits with DevOps, SRE, SecOps, platform engineering, and the compliance frameworks you already answer to.
- [Changelog](https://brocs.fyi/resources/changelog/): What changed in the BROCS framework, versioned and dated. Site tweaks do not appear here; changes to the framework itself do.