Approach
This page is the standard the rest of the site is held to: what a sentence has to be able to show before it ships, what the build checks on its own, and what the assistant is checked on before a shopper reads it. Each section names the mechanism, so you can go and look.
A page selling software has six familiar slots. On this site each of them carries something a reader can open and check instead, and every one of the six is a page that already exists.
The sources Refik reads, named one by one: catalogue, stock, collections, product copy, your policy pages, and the return and shipping rules you confirm in setup. What it reads.
A recorded session: thirteen exchanges with the storefront engine, each shown with the request that went out and the payload that came back, and all thirteen replayed against today’s code on every build. The session.
One decision inside the app, followed all the way through to the four sentences a shopper can hear, with the files it lives in named and the part still open written down. Writing.
The figures the app itself produces: the surfaces it answers on, the languages it ships in, the length of the trial, the conversation ceiling. Each one is marked in the HTML and compared against the constant behind it.
The access scopes Refik asks for, each with what it is for and where it stops — and the two that carry a write verb spelled out in full. Access scopes.
The price, the trial, the included conversations and the ceiling where billing stops, in one table that reads the same on any day you open it. Pricing.
Three of the six slots are held open by the build rather than by good intentions: a quote block, a percentage or a multiplier, and the name of another tool each fail on any page in this directory. The other three are a decision, and this page is where it is written down so it can be held against us.
Refik is built on that split. Every rule it follows is written twice: once in the words we hand the model, and once as code that reads what the model wrote back. The first is a request. The second is the one that holds. This site is held the same way.
A check makes a claim traceable rather than true. What it buys is that the day one of them goes stale, the build says so before you do.
What this site has to be able to show is one half. The other half is what the product has to be able to show in front of your shopper, where a wrong sentence costs you the order and the return.
Checked, not requested
A cosmetic that treats, cures, prevents or permanently changes the body is a drug claim. Refik’s draft answer is read sentence by sentence before the shopper sees it, and a sentence that crosses that line is held back.
It gets one chance to rewrite. If the second draft crosses too, the answer is dropped and the shopper is told plainly that the question needs a person, and asked whether to pass it to you.
What it says about a quiet field
“It only comes in one size.” “We don’t carry that.” Both are conclusions drawn from a field that came back quiet, and Refik stays with what the tool actually returned. Where it lacks the answer it says so, and points at the product page or hands over.
A product with more than one option has more than one price, so it gives the range, or each option with its own figure.
Read from your own data
Each option Refik puts in front of a shopper has passed two gates in your store: sellable, and in stock. An unbuyable suggestion costs more than silence, so the gates run before the suggestion is made.
Delivery dates, shipping speeds and return conditions come from the rules you confirmed in setup, and a discount reaches a shopper only when it came from your store.
The same checks run for a store whose sector the app cannot place. An empty rule set would have read as “this store carries no risk” when it actually meant “this store is unplaced”, so there is a base set every store gets, whatever it sells, and the app refuses to start when that set is empty.
Pricing is where a page like this usually gets vague. These are the answers as the billing code has them, including the two that run against us.
An empty slot is only honest while it is being worked on. Each of these has a condition attached to it, and the condition is a thing that has to happen rather than a thing we intend.
One of the three figures on the home page is reserved for it, and the note under them already says so. When it arrives it will name whose store it came from and what was measured.
Until there is one, every install button on this site goes to the setup steps, and the pages that take your money say plainly that subscribing has to wait for the listing.
A merchant saying something about their own store that we can point at and check — their sentence, their store, their name on it.
All three are conditions, and each condition is checkable from outside. A date beside one of them would be the first thing on this page that nobody can check.