Protocol Lab Is Live

Protocol Lab is live. The institution that authors the five sovereign layers of the Azul Stack is now open, publishing the reference architectures and specifications that national systems are designed and audited against.

Protocol Lab is not a product team and not a consultancy. Its output is specification: the API contracts, data models, and architectural rules that describe how identity, entitlements, oversight, interoperability, and infrastructure fit together in a sovereign system.

Azul Tech implements against those specifications like anyone else. That separation is deliberate. A specification that only its author can implement is not a specification, it is a manual for one product.

Governments across the continent keep buying systems that work and still cannot be built on. The software runs, the vendor is competent, and yet five years later the ministry cannot connect a second system to the first without going back to the same supplier, because nothing about how the first one works was ever written down in a form anyone else could use.

That is not a procurement failure. It is a documentation failure with procurement consequences. Publishing the specification openly moves the asset from the supplier to the state.

A specification written once and published openly can be implemented in many countries by many teams. Six nations exchanging road crash data need one agreed protocol, not six bilateral integrations.

This is what documented for the continent means in practice: engineering whose value survives the departure of the firm that wrote it.