v1.0.0-rc.1

[expede]

Preview 📚

Splitting out promises and pipelining from Invocation, since it's not required for a bunch of use cases. It also makes each spec more focused.

[bgins]

Suggested change

	An Action Identifier (ActID) is the content address of an [Action]. It can be found direction in an Invocation:
	An Action Identifier (ActID) is the content address of an [Action]. It can be found directly in an Invocation:

[bgins]

Suggested change

	A Receipt MAY have multiple input addresses. For instance, if an Action contains a promise versus when it's fully reified, the associated Receipt is the same.
	A Receipt MAY have multiple input addresses. For instance, whether an Action contains a promise or is fully reified, the associated Receipt will be the same.

Possible rephrasing.

[bgins]

Suggested change

	Using a shared cache[^bbd], many cooperating processes can collaborate on multiple separate goals while reusing each others results. The exact mechanism is left to the implementation, but [pubsub], [gossip], and [DHT]s are all viable.
	Using a shared cache[^bbd], many cooperating processes can collaborate on multiple separate goals while reusing each other's results. The exact mechanism is left to the implementation, but [pubsub], [gossip], and [DHT]s are all viable.

[Peeja]

It looks like [Action](https://github.com/ucan-wg/invocation#31-action) is now a broken link. In fact, it looks as if "Action" is no longer defined. Is that right? Actions are mentioned a couple of times there, but not defined explicitly, and it looks like it may be leftovers from a previous revision?