Licence
What you may do with the BvLogic specifications and the conformance harness: CC BY 4.0 for the standards, MIT for the code, and an explicit list of what is not covered.
Published 2026-08-12. What you may do with the specifications and the conformance harness, stated so you do not have to ask.
Why terms at all
A specification nobody may copy is not a standard, it is marketing in the shape of one. The whole argument for publishing BEIS, the Autonomy Ladder and the rest is that somebody outside this company might operate against them and disagree, and neither operating nor disagreeing is possible if the legal position is unstated. Silence is not permission, and a careful enterprise lawyer will read silence as no.
The grants
The published specifications — CC BY 4.0
BEIS · The Autonomy Ladder · Process Autonomy Classification · Enterprise Digital Twin Standard · The Enterprise Constitution · The Enterprise Outcome Record · The Autonomous Action Record · The Human-to-AI Leverage Ratio
The conventional choice for a specification somebody is meant to implement. It permits copying, redistribution, adaptation and commercial use, and asks only for attribution. An implementer can build a product against these documents without asking us, which is the entire point of publishing them.
- You may implement these specifications in a commercial product without permission or payment.
- You may republish them, in whole or in part, with attribution.
- You may adapt them, and you must say that you changed them.
- You may not imply that we endorse your adaptation.
The conformance harness — MIT
beis_conformance.py
It is code, and it exists to be run against systems that are not ours. MIT is the least friction available: no copyleft obligation to worry a corporate legal team, and no ambiguity about running it inside a commercial environment. A harness with a licence somebody has to think about is a harness nobody runs.
- You may run it against any system, including in commercial and internal use.
- You may modify it and redistribute it.
- It comes with no warranty, which for a measurement tool is the honest position: it reports what your system returned, and it cannot know whether that was correct.
What these do NOT cover
Being explicit about what a licence does NOT grant is more useful than the grant itself, because this is where a reader would otherwise guess.
- The BvLogic name, logo and wordmark. You may say your system conforms to BEIS 0.1; you may not describe it as BvLogic Certified, because no such certification exists and we have refused to create one while we would be the assessor.
- Our published measurements. The benchmark results describe our system on a date. You may cite them with attribution; you may not present them as yours.
- The website's own content outside the specifications, which is not covered here.
- Any implication of endorsement, conformance testing, or that we have reviewed your implementation.
Attribution
BvLogic Enterprise Intelligence Standard (BEIS) 0.1, BvLogic Solutions LLC, https://bvlogic.com/standard/
Attribution names the version. A specification cited without one is unfalsifiable: a reader cannot tell whether an implementation matches the document it claims to follow.
The part that costs us something
A licence permitting adaptation means somebody can publish a changed BEIS and call it BEIS. That is a real cost and it is the correct trade: a standard that cannot be forked cannot be adopted either, because adoption means implementers changing things we got wrong. The protection is not a restriction, it is version identity - each specification carries a version and a published date, so a modified copy can be compared with the original rather than mistaken for it.
A note on changing these
These are the conventional choices for each artefact type, not the only ones. Changing them is a commercial decision and reversing a permissive licence for material already published does not un-publish it: anyone who took a copy under these terms keeps those terms for that copy. That asymmetry is why the choice is worth making deliberately once rather than casually twice.