Done at the end of the spring. Possible outcomes:

1. A t-shirt sized epic that represents with confidence the work required from the MCO to deliver the MVP of Confidential Computing.
2. T-shirt sized options of possible paths and trade-offs to deliver the MVP of Confidential Computing.
3. Additional, specific spikes to be able to arrive at understood work.

This Spike is time-boxed to 1 sprint for 1 dedicated person plus 1 week involving other contributors.

Current understanding is that some changes to the MCO are required for an MVP:

1. MCS changes
   1. Option 1: MCS pushes the config to Trustee instead, which will serve them
   2. Option 2: Adapt MCS to only serve configs to attested nodes
   3. Option 3: Operator acts as proxy to the MCS
2. Need bootc in place
3. Changes to bootimage management?