Actionpack

> _If you can't discipline that animal, I'll have to take it away from you._

* Failed `Action` instantiation no longer interrupts


Tar Checksum (SHA256)
1d14e8c28fe8b95cf568c95651f2410ae299738ab78c50997ef7f2f1ae207d35

> **Ava:** _Isn't it strange, to create something that hates you?_

* No wasteful argument unpacking when instantiating a `Procedure`
* Better object representations for `Procedure` and `Result`


Tar Checksum (SHA256)
8925872ff62fdacc4770568a16d6deefaaf16c086fae89ac12940cc978fdbe70

> **Nick:** _No man, you got, you gotta, you gotta promise definitely._

* ReadBytes/WriteBytes -> Read/Write
* can `Write` to standard out/err
* adds flexibility in choosing `Action` kwargs via `Pipeline.Receiver`


Tar Checksum (SHA256)
cfe6de0eaa2ae3a3c9648fc20a6f1eacd5bbe0ed9c80968179a4f778dbeca162

> **Baby-O:** _What's wrong with him?_
> **Poe:** _My first thought would be, 'A lot'._

* introduces the `Pipeline` abstraction


Tar Checksum (SHA256)
a7c4a123a4d9f03ff7611f0c8a0789f8559cec008d9b909bf596c2d4f754bf7e

* an `Action` definition can declare internal requirements via the class declaration kwarg, `requires`.

Tar Checksum (SHA256)
70537e63fde96818d8ab50b89ba17e3c66c8a82c58a18f58b34ced094e32ff72

* `Procedure` execution concurrency governed by boolean method option, `synchronously`.

Tar Checksum (SHA256)
be731cf769bdd7f53d748f79ad0c5468f8ef03ad6ed6048dd8564247bff35a20