One of the most important questions facing the BBCO community is about boundaries. Where does structural observation of governance behavior end, and where does professional interpretation begin? Getting this line wrong in either direction causes real problems.
If the community reaches too far into interpretation, the methods lose their neutrality and become a tool for advocacy. If the community stops too short, the outputs are technically sound but useless to the people who actually make governance decisions.
This post explores that boundary to make the current thinking visible.
The BBCO pipeline produces structural observations. These include:
These are measurements. They describe what happened structurally. Whether that structure is good or bad, adequate or deficient, compliant or otherwise, belongs to the professionals who carry that authority.
The pipeline stops short of:
This is a design choice. The moment the community embeds interpretive logic into the shared infrastructure, the outputs become opinions. Opinions require accountability. Accountability requires authority. Authority over regulated organizations belongs to regulators, boards, and the professionals who serve them.
Risk managers, actuaries, and captive boards bring something the pipeline cannot: context. They know that a spike in termination depth variance in Q3 coincided with a leadership transition. They know that a particular domain crossing pattern reflects a deliberate reorganization, not a governance failure. They know which patterns are concerning and which are expected.
The pipeline gives them better raw material to work with. Instead of relying solely on loss data (which is lagging and sparse) or subjective assessments (which are hard to compare across organizations or time periods), they can look at structural behavior captured consistently.
The interpretation is theirs. The evidence is shared.
In practice, the boundary between observation and interpretation can blur. Two examples:
Example 1: Variance acceleration. If termination depth variance is increasing quarter over quarter, is that an observation or an interpretation? The BBCO position is that computing the acceleration is observation. Saying the acceleration is "concerning" is interpretation. The community computes and publishes the metric. The professional decides what it means.
Example 2: Peer comparison. If two captive programs in the same industry show different domain crossing patterns, is presenting them side by side an observation or a judgment? The BBCO position is that the comparison is structural. Saying one pattern is "better" is judgment. The community provides the comparison tools. The professional assigns meaning.
These edge cases recur as the pipeline evolves. The community's role is to keep the line visible and to err on the side of restraint when it is ambiguous.
If BBCO drifts into producing ratings or recommendations, two things happen. First, the outputs become contestable in a way that requires institutional authority to defend. An open-source project lacks that authority. Second, the shared infrastructure becomes less useful, because every organization that disagrees with the embedded interpretation will fork or abandon the tools.
Neutrality is what makes the shared work durable across jurisdictions, organizational types, and regulatory regimes.
The people who make governance decisions already carry the authority and the accountability. The community's job is to give them clearer evidence. That is enough. It is also the hardest part.
The most useful tool is one that shows you what happened without telling you what to think about it.
Read more from the BBCO community.