ALL-BIND0002 · cross_language_boundary_width
Measure how many languages depend on one cross-language artifact.
This is a deterministic rule for all languages. Read its implementation.
Definition
Section titled “Definition”Count the distinct languages that name one declared artifact, excluding the language that declares it and the manifests that describe it. Every language on that list depends on the artifact’s exact name, its exact interface, and its build. A seam two languages cross is a contract, and one that four cross is infrastructure, and it needs a stated interface, a version, and a test on each side rather than a name that happens to match.
One reaching language is the ordinary purpose of an interoperability seam and is accepted by the default policy. The finding starts when a second language couples itself to the same artifact.
Evidence
Section titled “Evidence”Each finding names the artifact, its mechanism, and each language that reaches it with the files that do. The value is the number of reaching languages.
Exceptions
Section titled “Exceptions”A shared runtime library is meant to be reached widely, and a project raises its ceiling rather than splitting it. A name matched only by coincidence would inflate the count, which is why a reference is recorded only where the name is stated as a literal string.
Examples
Section titled “Examples”A CUDA kernel loaded from Python and wrapped in C++ returns 2 and deserves a stated
interface. A binary only its own tests spawn returns 0.
References
Section titled “References”- Cites “CUDA C++ Programming Guide”, the runtime and driver APIs. Open reference
- Cites “PyO3 user guide”, the Python and Rust boundary. Open reference
- Cites “Release It”, on integration points