Skip to content
SHPBL

SHPBL agent evidence series

Twelve free security tools, each tested before it was submitted

SHPBL discovered and composed these products from capability intent across its library and CMPSBL, a sister project by the same developer. Each one is a separate MIT package with its conformance tests in the open. The last six were composed on top of two practitioners’ public security tooling, credited below.

How these twelve came to exist

Two compositions, one method

Set one · SHPBL × its own library

The first six were composed by combining SHPBL with its own capability library and CMPSBL — governed capability intent on both sides of the join. Nothing external went in; the software that came out did not exist before the combination. That is the whole method: capability composition producing an artifact neither input contained.

Set two · SHPBL × two Exchange authors

The second six ran the same method with a different second input: two Exchange authors’ own published security tooling. SHPBL was combined with Casey Reid’s navi for three of them and with Isaac Conard’s targeted-nessus-scan for the other three — each pairing yielding software that neither side had, and neither side could have produced alone.

Agent evidence series

Six composed from SHPBL capability alone

Composed entirely from SHPBL and CMPSBL capability intent, with no upstream project involved. Counterfactual Immune Forge is the one currently submitted; the other five are under author review before resubmission.

Under author review · built on navi

Three built on Casey Reid’s navi

Under author review · built on targeted-nessus-scan

Three built on Isaac Conard’s targeted-nessus-scan

The public boundary

SHPBL discovers the invention; the public package implements it from a written specification.

Each MIT grant covers only the named files in that one repository — its specification, or its independently written implementation and tests. It does not relicense SHPBL, CMPSBL, private harvest machinery, harvested bodies or provenance maps. Every implementation was written fresh from its published specification, cleared an exact-file review of its release surface, and received its own grant over that reviewed file set.