Kevin Hoffman

The lattice should be able to receive block notifications on actors, host IDs, and capabilities. Host IDs aren't supported now, but they will be after the #41 anti-forgery story is...

Capability Providers should Identify Themselves to Actors During Dispatch

1

When a capability provider uses the dispatcher component to put a request on the message bus to be handled by an actor, the only information the actor module is given...

Adopt the new WIDL code generator (this will likely be a breaking change for actors and providers) Also, split the codec so that it's no longer a monolithic crate but...

Once the new WIDL code generation functionality is available from waPC, build the tinygo actor SDK with examples

AssemblyScript Actor SDK needs more examples, and it needs to be brought up to the new codegen standards being worked on for WIDL in [waPC](https://github.com/wapc)

If an actor has a `tag` in the form of `alias-(alias name)` where "alias name" is a URL-friendly alphanumeric string with no whitespace or special characters, then the actor can...

An [OpenFaas Provider](https://docs.openfaas.com/architecture/faas-provider/) exposes a RESTful API that allows for the interrogation of which functions are available to be invoked and also supports the invocation of those functions. Any actor...

Create a single CLI to encompass all waSCC tooling

1

This tool should enable all developer and operations tasks related to waSCC, lattice, and gantry. It will supercede all existing binaries with the exception of the waSCC host binary itself:...

waSCC should support the ability for actors to perform asynchronous host calls to either capability providers or to other actors. This will require making a little bit of change to...

The lattice will realize its full potential once it can support things like declarative deployments of actors and capabilities. To support those kinds of features, we need an autonomous agent...