Product Station · Commerce
Terre & Table
Build a fine-food selection by taste and budget, then choose delivery.
The control station, in brief
This station sits between your agent and the tool. Before any call, it checks who is acting, shows only the useful tools, applies the rules below and keeps track of the task.
It can
- Search products
- Build a selection
- Choose delivery
It asks a human for
- Go over the budget the customer gave
It never has access to
- Pay on the customer's behalf
Scenario Replays
An agent works through the station. Simulated scenarios, no real data, no key required.
Copy the station, change a limit or an approval step in its configuration file, and get your own station.
The configuration in detail
Everything the station does fits in this file. The replay above applies it, and a copy starts from it. The values are examples to adapt, not a recommendation.
station:
id: terre-table
kind: product
policies:
- {policy: budget-respected, at: submit}
global:
language: en
timezone: Europe/Paris
apis:
- id: terre-table-shop
operations:
findProducts: {access: read}
buildSelection: {access: write, risk: low}
chooseDelivery: {access: write, risk: low}
# not listed, so not available to the agent:
# submitOrder
profiles:
shopper:
allow: [findProducts, buildSelection, chooseDelivery]
policies:
budget-respected:
type: rule
when: "action == buildSelection and total > customer_budget"
effect: needs-human
reason: "Above the stated budget, the customer confirms."
skills:
- {id: find-products, uses: findProducts}
- {id: build-selection, uses: buildSelection}
- {id: choose-delivery, uses: chooseDelivery}
playbooks:
- id: compose-a-selection
tasks: [find-products, build-selection, choose-delivery]Shared copies
Copies that their authors choose to share will appear here. Each one keeps a link to this original station.