ALL-BIND0001 · unreached_cross_language_artifact

Report an artifact one language declares that no other language reaches.

This is a deterministic rule for all languages. Read its implementation.

Definition

Report a binary, native module, shared library, or kernel a repository declares where nothing outside its own language names it. Such an artifact is either dead weight that still has to be built, released, and kept compiling, or a seam whose other side was never wired. Both cost, and neither is visible in an import graph, because the caller and the callee never share one. Only an artifact declared to be reached across a language boundary is judged this way.

Evidence

Each finding names the artifact, the mechanism it is reached through, the manifest or source that declares it, and every file that names it. The result reports whether the artifact stands unreached.

Exceptions

A console script is a command a person types, so the packaging entry point a manifest installs names a callable its own language already holds and is never judged here. A published binary, a library another repository consumes, and a plugin a host loads at runtime all have their callers outside this tree. A project excludes what it ships rather than deleting it. A name reached only through a variable this scan cannot follow also reads as unreached, which is why the finding names the files it did see.

Examples

A Cargo manifest declaring mcmr-kernel that Python spawns is reached and passes. The same binary with no Python caller left after a refactor is reported. A pyproject.toml installing the mcmr command through project.scripts is not reported, because that entry point is the shipped product rather than a seam.

References

• Cites “PyO3 user guide”, building and distributing a module. Open reference
• Cites “pybind11 documentation”, module creation. Open reference
• Cites “Python Packaging User Guide”, entry points and console scripts. Open reference