Developer examples

One pattern at a time.

Start with the shop, then explore focused examples of app-owned tools, guards, forms, and typed judgments.

Main example

Everyday shop.

Browse products, build a cart, and try a simulated checkout. Use the controls yourself or ask the assistant.

01
Inventory
Pi reads the current merchandising table and can only call narrow selection and sorting tools owned by the app.
↗
02
Invoices
Pi chooses each account-receivable action from actual tool results, but invoice mutations require explicit confirmation before records change.
↗
03
Commerce
Pi can search products and edit a cart, while stock guards and checkout confirmation prevent unsafe purchases.
↗
04
Flights
Pi can fill the flight search controls and select one visible result without leaving the app-owned itinerary state.
↗
05
Support
A visible support form becomes a tool, and ticket updates stay constrained to the current board and schema.
↗
06
Resolve the right requests
Read what customers mean. Select the right requests, then prepare replacements.
↗
07
Find what actually fits
Describe your day. Compare headphones against the way you will use them.
↗
08
Check the evidence
Compare each claim with its source. Open the mismatch and request better evidence.
↗
09
Get to the right help
Describe what happened. The next step changes with the meaning of your problem.
↗
10
Launch triage
Score reports, change priorities, and confirm a team assignment.
↗