I keep seeing everyone guessing what the margin is on inference. You say that it's largely break even. We have this person in the thread claim 80% margin (https://news.ycombinator.com/item?id=45462442).
Rate cuts are priced in at about 100% for a 1/4 point. It might go up for a 1/2 point, but that may also signal fear which could have the opposite effect. I think it's hard to say at this point.
The Federal Reserve operates under a "dual mandate" from Congress to promote maximum employment and stable prices (low inflation). As unemployment rises, the Fed will lower interest rates to stimulate investment (increase employment opportunities).
There are definitely some similarities. I think the main difference is the compatibility of Wasm / WASI. Often for unikernel / libOS, you would need to recompile applications to target the specific unikernel / libOS. The goal is that you should be able to take a component that you would run with Wasmtime or other component model compatible runtime and be able to run that on Hyperlight-Wasm.
As for executing a tree of connected components, in the current state of Hyperlight-Wasm you'd probably want to take a collection of components and compose them together using something like https://github.com/bytecodealliance/wac to create a final component composed together from multiple components.
A Wasm component running inside of Wasmtime is just fine. However, when you start to use resources from outside of Wasm, e.g. systems, network interfaces, GPUs, etc., Wasmtime uses OS resources from the host that it is running upon. If this host is running on your trusted compute base, then it implies you are trusting the host implementations in Wasmtime, which for some is just fine. However, Hyperlight-Wasm gives platform builders the ability to describe the interface between the guest and the host explicitly, so you could only expose the host functionality you would want with the trusted implementation you'd want. For example, if I'm building a FaaS, I may want to provide only an exported event handler and an imported key/value interface to the guest for which I've built a safe, multi-tenant implementation and strictly disallow all other host provided functionality.
These numbers are complete make believe.