...

If you have created child picos, they will also be visible on this page, each joined to its parent pico by a solid black 3px line. Each pico can be dragged to move it to a different location on the canvas. You can also drag a corner to reshape and resize it.

...

More detail for a single pico

A single left mouse click on the name of the pico will open it up for a more detailed look at the properties of your root pico.

...

UI tabs

The information about the pico is organized with tabs.

...

It begins with a list of the rulesets currently installed in the pico. A newly created pico will come with three rulesets installed.

• io.picolabs.pico-engine-ui which allows picos to interact with the UI. This ruleset cannot be deleted.

• io.picolabs.subscription which allows the pico to establish a two way relationship with another pico. This ruleset can be deleted if not needed.

• io.picolabs.wrangler which is a kind of operating system for the pico, described more fully in the Wrangler page. This ruleset cannot be deleted.

A checkbox to the left of each ruleset identifier (RID) when checked will allow you to see more information about this ruleset, and buttons to "flush" and "uninstall" the ruleset. You will see the URL from which the ruleset was installed. If you know the content of the resource at that URL has changed, you should click the "flush" button. When you do so, you will see that its hash changes, along with the "Last flushed" date.

...

Channels can be deleted (with the exception of family channels). Deletion cannot be undone, so be careful. Doing so revokes the ability of outside applications to use the ECI again.

The form at the bottom of the tab allows you to specify tags, an event policy, and a query policy. Clicking on the "Add" button creates a new channel for your pico.

Logging tab

This tab allows you to see detailed logging information concerning events and queries sent to the pico within the last twelve hours.

...

This tab will let you see the latest transactions (either events or queries) which the pico has processed. Click on the checkbox to see detailed logging.

See also the Developer UI -- Logging tab page.

...