Activity

What the surface does

Activity is everything after the sale: orders and their tracking, the satisfaction sample, and the support agent that answers your customers. It is the part of the product that keeps running when you are not looking at it.

Orders and tracking

Order lookups are founder-scoped by construction. The resolver requires the caller’s own claims and has no unscoped form, so a product you do not hold cannot appear in your orders. An order id belonging to someone else reads identically to one that does not exist — the difference between those two answers would otherwise be a way to guess at other people’s order ids.

An empty desk is a named state with a sentence, not a blank list and not an error. Nothing here is seeded with sample orders to make the screen look busy.

Satisfaction sampling

Satisfaction is a sample, and it is reported as one. The rule the module exists to enforce is that no score is emitted at sample size zero — not nought per cent, not “not applicable”, not a neutral midpoint, not an empty chart with an axis. The field is absent, because a number on screen is a claim that something was measured.

Below three responses, no score is stated at all: a mean over two answers is an anecdote. That floor binds symmetrically — too few responses to state a score is also too few to state an improvement or a decline. Where a figure is shown, its sample size travels with it, because a satisfaction figure without its n reads as a finding when it is an artefact of how few people replied.

Alongside the score, the surface reports what customers actually said as counted words from their own comments rather than a sentiment label, so you can check the summary against the responses instead of trusting it.

The support agent

The support agent answers your customers’ questions about your product, assembled from that product’s own record: its specifications, the offer row with its observed figures and their bases, and the store manifest. A question it cannot answer from the record is refused by name — “we do not have that on record, so we will not guess” — and handed to a person.

Two constraints are enforced on its output rather than trusted to its instructions:

• It never states a shipping cost, customs charge, duty, import fee or delivery caveat. The outgoing text is scanned, because a rule that lives only in an author’s intention is not a control.
• The tense rule carries through. The undercut was observed and may be stated flatly. The margin is declared and is never quoted to a customer at all. A price carries the date it was checked, and any failed refresh, through the same resolver the offer screen and the storefront use.

Where the store has no returns or warranty terms on record, the agent says so rather than stating one.

Honest limits

• Order-update email is composed from the record; it is sent from an address a customer can reply to, and it never fabricates a delivery date.
• The support agent has no authority to issue a refund, change a price, or alter an order. It answers.
• With no customers yet, this surface reports that plainly and fills in as orders arrive.

What the operator does with all of this lives in admin, and the boundaries on the agent’s authority are set out under product security.