...
One of the first things to get out of the way: the pico API is not RESTful. Picos don't present a collection of resources to be manipulated by GET, POST, PUT, and DELETE. The However, the API does rely on HTTP transport, but it we also have an SMTP transport for events. So HTTP and it's methods are just a transport for the pico APIits methods for transport. If you've gotten REST as a religion, this may seem like sacrilege, but it's really a matter of using the right API for the job. RESTful APIs are great for request-response style interaction, but not so good for the evented interactions that picos support.
...
Similarly, the Sky Cloud API defines the patterns for queries that a pico understands. Again, this is a meta-API, since the queries that any given pico responds to depend on thethe modules installed. Queries are thus implementable with different code than the event processing and, in practice, tend to be much faster.
...
In the systems we're building now, picos donwon't get be created as empty vessels waiting for rulesets and modules to be installed and their API to be defined. Instead, we use CloudOSwill have a way to create picos of specific types and they that come pre-loaded with rulesets that implement CloudOS Wrangler and other services. Thus, when you'll create a pico to represent a vehicle, it comes will come with the CloudOS event-query API as well as rulesets that provide an a more specific vehicle collections event-query API for Fuse along with a pre-defined data schema. This makes picos very powerful and gives developers significant leverage.
...