# Manifesto

> Why BROCS exists, why these five and no other set, and what the framework is arguing against.

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

---


BROCS is how we came to think about the surface where AI apps and agents meet the
enterprise. Five parts: Build, Run, Observe, Control, Secure.

It started with a question a healthtech engineering leader asked after weeks of
evaluating the AI tooling market: "I need somewhere to build it, somewhere to run it, a
way to see what it's doing, and ensure it doesn't go off the rails." That sentence is
Build, Run, Observe, Control. Add Secure for the conversation with the CISO, the
compliance officer, and the regulated buyer, and you have the full surface.

Most AI products occupy one part of that surface and push the other four onto "your
infrastructure" or "your governance tooling". Customers integrate across three to five
products, contracts, and audit processes, and the integration cost eats the productivity
gain. A reasonable executive then concludes AI does not work for the enterprise, which is
not the lesson the experience actually teaches.

## What BROCS is

- A **vocabulary** for the whole surface, so buyers and builders can name what they are
  missing.
- A **checklist** to run before adopting any AI tool: which letters does it cover, and
  what happens to the rest?
- A **lifecycle**, drawing on DevOps, SRE, SecOps, platform engineering, and control
  theory, applied to AI adoption.

## What BROCS is not

- Not a product. Not a vendor pitch. Any platform, commercial or homegrown, can be scored
  against it.
- Not a maturity model. You do not finish Build and move on; the letters are continuous
  and the last one hands back to the first.
- Not a compliance framework. It sits alongside the ones you already answer to and asks a
  different question: can your platform produce the evidence they want without a project.
- Not "just give everyone Copilot". Assistants are one tile on the Build surface. The
  framework is about everything that happens after: where the things people build go,
  what they connect to, and how you keep them in check.

## What it is arguing against

Three things, specifically.

**That the tile is the product.** A coding assistant covers a corner of Build. Sold as an
AI strategy, it manufactures demand for four letters nobody has staffed.

**That the integration cost is somebody else's.** One tile per vendor times five tiles is
three to five contracts, integrations, identity wirings, and audit processes. That cost is
real, it lands on the customer, and it is where the productivity gain goes.

**That partial coverage is a stage.** It is presented as an early phase of a journey. In
practice organizations sit at partial coverage for years, and the
[failure-mode library](/resources/failure-modes/) is what happens during those years.

## The five theses

1. **Tool churn is a given.** The enablement layer has to sit underneath the tools, or
   every switch is a re-platform.
2. **It goes where your data goes.** One system with multiple placements, not a migration
   plan.
3. **Sovereignty is a requirement, not a preference.** For some organizations it is a
   legal gate, and the sovereign paths have to be live options.
4. **Integration cost is the silent killer.** It is the mechanism by which a real
   productivity gain reads as net zero.
5. **Structurally it is an operating system.** Five parts that assume each other, a
   foundation apps, agents, and governance run on.

## Origin

BROCS was coined by [Leo Mata](https://leomata.com/), who builds enterprise AI
infrastructure at [Calliope AI](https://calliope.ai) and kept watching the same five gaps
swallow adoption projects. The original write-up is at
[leomata.com/blog/brocs](https://leomata.com/blog/brocs/), and that post remains the
origin citation. This site is the canonical home for the framework.

The framework text is published under
[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Copy it, translate it, argue
with it, put it on your own slides. Attribution to brocs.fyi is the only ask, and
disagreement is more useful than agreement: if a letter is wrong, the framework should
change.