The typestate pattern is a powerful tool for enforcing that an object is always in a correct state,
— defined by object’s type — and, moreover, state transitions are always valid.
These and couple of other useful properties are all checked at compile time.
In order to increase profitability, attestations must be aggregated in a way to cover as many individual
attestors as possible. Let’s explore the ways to do such an aggregation.
It is quite common situation when you are building Docker images: some secret value/file is needed (temporary, for the
duration of the build), and you are puzzled how to pass it w/o over-exposing, and make it accessible down the road, when
the image becomes publicly available.
