Composable primitives for accessing cloud data in your steroids application.
The part that kinda looks like ActiveRecord. Allows you to declare a remote resource as a set of named actions relating to that resource.
The part that consumes data structures and spits out types. Allows you to build type validators based on descriptions from a remote source, eg. JSON-Schema.
The part that looks like a bunch of type annotations. Provides validator functions that allow you to tell a type from another and use that information in a schema.
The part that goes around actions on a resource or ad-hoc use cases of it. Allows you to worry less about accessing the same data in multiple webviews or on multiple occasions.
The part that drives your consumption of resources. Provides ready-made strategies for determining when the data is needed.