Kevin Hoffman

Some random thoughts: Wasm specification makes no assumption about the existence of a browser. Go's implementation baked in the JavaScript interaction and usage patterns and as such is nearly (and...

1. This is entirely up to the developer. I would say the easiest to do would be to create an actor as mentioned above that just listens on a specific...

re: 3 - we'd probably also want to implement some retry where it will attempt to get back into a state where it's evaluating policy. Also, if policy answers are...

I've added some detail to what payload shape and meaning appears on the `WASMCLOUD_POLICY_CHANGES_TOPIC`

>Re: re: 2 We should make sure we document that you shouldn't run the policy actor (if you are using one) on the lattice nats when we create this Agreed...

Only one action is ever intended to be evaluated at once. In other words, there's no expectation that the host would check multiple call types in a single request. Also,...

Ok I'll edit make that change in a bit. Couldn't figure out which syntax was more clear.

I think now that there are PRs that implement this, we should update the wasmcloud.dev docs accordingly to have a section on enabling policy enforcement. Then, if/when the API changes...

I am definitely in favor of not relying on any particular version of OAM for this. The underlying `lattice-controller` could change its manifest format from an OAM YAML file to...

When `HostCore.Host.purge` is called, the capability providers are given the chance to gracefully shut down and this gives the highest chance of not orphaning the child processes. Otherwise, this is...