Contribute
CIRCUIT is a practitioner-built standard, and its credibility depends on practitioners stress-testing it. The framework launched from a single organization. The goal is for it to outlast any one organization — and that only happens if the community that uses it also shapes it.
If you have adopted CIRCUIT, challenged it, found a gap, or seen a scenario it doesn't handle well, that is a contribution. Here is where to start.
What We Are Looking For
Every one of these makes the next version of the framework stronger — whether it confirms what works or exposes what doesn't.
Deployed CIRCUIT in your environment? Tell us what worked, what didn't, and what you had to modify. Real-world evidence of how the framework performs is the most valuable input at this stage.
Share an adoption report →The Interpretability Maturity Score is only as good as the tooling that supports it. If you have used SAELens, Neuronpedia, Goodfire, the Anthropic circuit-tracer, or any other interpretability tool in a production context, share what artifacts you produced and what IMS level they supported. The tool references in the framework are a starting point, not a closed list.
Share IMS evidence →The legal feasibility floor — minimum IMS levels by regulatory domain — is one of the highest-leverage additions in v1.2. If you operate under ECOA, EU AI Act, FDA CDS, HIPAA, SR 11-7, CMMC, or SEC/FINRA obligations and have a view on what IMS floor is defensible in your domain, we want to hear it.
Propose a mapping →Sent the "Show Me Your Circuits" questionnaire to a vendor? What did they say? What questions confused them, and which produced useful signal? Every response — or non-response — informs the next version.
See the questionnaire →Found a scenario the framework doesn't handle? A rule that conflicts with another? A use case where the CRS formula produces a nonsensical result? Open an issue. That is exactly how v1.2 gets built.
Open an issue →How to Contribute
CIRCUIT uses GitHub Discussions as its primary community space — no Slack, no mailing list. That is intentional. The target audience is CISOs and security architects, not developers, and the format rewards substantive posts over real-time noise.
Releases follow major.minor.patch.
Recognition
Contributing to CIRCUIT is a visible, on-the-record act — for you and for your organization.
Every accepted contribution is credited in the release notes by name or alias, your choice.
If your organization adopts CIRCUIT, we will list you as an adopter on the framework site — a signal to your peers, your auditors, and your vendors that you took interpretability governance seriously before it was required.
Start a discussion with an adoption report, open an issue to flag a gap, or read the framework to see where it stands today.