get first paper and add meta-review

trust/EMSOFT24/future_work.tex

@@ -0,0 +1,20 @@
+
+They will say, you have a nuclear power station, something happens, you just drop the trust a little bit, the thing, but the thing blows up.
+How do you put a violation in relation to how much it drops?
+
+Then have in the discussion something where you just say, oh, different violations can have different, can affect the trust differently.
+
+For your case study, you chose the same value for all of them, but you have this in the discussion and show really somehow that it stands out, that you say, oh, here's an example configuration with different values.
+
+So you could look at that, your short term values will reflect that.
+
+
+And if you have more than that, then every, so you have a short term trust coming out, which is for each of those weighted things. And now you can say there is a severity of an event is associated with short term and it reflects stands out. And that's the weightage that actually goes into your commutative long term thing.
+
+
+Instead of having just two or three vertex or you can have many because and also you have a severity of events associated with them. So given the severity, there is a weight associated that can affect the short term and the short term will eventually affect your long term. And depending on what weight comes in, your long term trust might drop substantially.
+
+For example, a car experiences stutter, meaning the engine, like you have to sometimes, oh, it misfires or it doesn't start anymore for after trying to trace. I mean, these are two substantially different ways to affect trust in the vehicle.
+
+
+You could just do that on a BIOS example that we have, right? Sometimes it's checking for an external USB device and it takes time to boot up. But sometimes let's say your boot up has just been messed up and it doesn't go beyond a certain state. It's stuck at that blue screen. Now you have two different stages.