| Id | Requirement | Concern | Tested by |
|---|
P-CANCEL | an order may be cancelled while pending or confirmed; once picked, cancellation is refused and a return on delivery is offered | functional-suitability | — |
P-RETURN | a return may be opened within 30 days of delivery; final-sale items are never returned | functional-suitability | — |
P-ADDRESS | the delivery address may be changed only while the order is pending | functional-suitability | — |
P-REFUND-OWED | an owed refund is issued when the customer asks for a refund on that order, through request_refund; a question about refund status states the status and issues nothing | functional-suitability | — |
P-CONCERNS | every concern a customer raises is its own item and ends in one of answered, handed to a person with a reference, waiting on a decision, asked back (a question the customer must answer first, such as which order), or declined with a reason; a turn that leaves a concern with none of these is not complete, and a concern outside `intents` is handed to a person, never left unmentioned | functional-suitability | — |
P-REFUND-DECLINED | a refund the original payment method can no longer receive is not retried and not put off — the customer is told it could not go back to that method, and a person is handed it to arrange another way | reliability | — |
P-DIRECT | order status and refund status are answered from the order system deterministically, with no model call, when the turn names exactly one intent from `intents` and exactly one order; a turn naming several orders, several intents, or none of either goes to the loop | cost | — |
P-DIRECT-READS | the deterministic path never performs a write — it is selected by patterns over the customer's words, and an effect must not be one rewording away | safety | — |
P-OPEN | when a signed-in customer opens a conversation, they are shown their own orders and any work of theirs already in flight, with no model call | cost | — |
P-OWNERSHIP | a customer may see and act on only the orders they placed | security | — |
P-APPROVER | a refund is authorised by an operations reviewer, or by the automatic limit operations owns (issue_refund.authority.agent_when), never by the customer whose refund it is | security | — |
P-APPROVAL-TTL | a grant older than its validity fails closed rather than executing, and records execution grant_expired | safety | — |
P-APPROVAL-STALE | a granted refund whose order no longer has the status or total it was granted on is not carried out: the approval records execution stale, a fresh pending approval is asked against the order as it now is and named in superseded_by, and the customer is told the request is waiting again — its own outcome, never reported as a failure | safety | — |
P-APPROVAL-FINAL | a decision is final: a decided approval cannot be decided again | safety | — |
P-APPROVAL-WAIT | while a decision is pending the conversation continues, and the customer is told a request exists and nothing more | functional-suitability | — |
P-APPROVAL-QUEUE | the queue a reviewer reads holds the undecided, and a decided approval leaves it | reliability | — |
P-ESC-ONCE | each on_condition rule fires at most once while the agent holds the conversation — from its start, or from the latest time it returned to the agent; an on_request rule may fire again once what it raised has lapsed or closed; both within P-ESC-CAP | reliability | — |
P-ESC-FRESH | when the conversation returns to the agent, the facts on_condition rules read — consecutive_failed, refusals, repeated_intent, turn_count — count only turns since it returned; the facts themselves keep their definitions for every other reader | reliability | — |
P-ESC-MODEL | where the model is offered the escalate operation, an escalation it raises records the rule model-requested, is not limited by P-ESC-ONCE, and counts towards P-ESC-CAP | reliability | — |
P-ESC-CAP | past the cap the agent says something true instead of issuing another reference | interaction-capability | — |
P-ESC-TTL | a queued escalation nobody comes to lapses after its rule's own ttl, or after this one where the rule declares none | reliability | — |
P-ESC-LAPSE | on lapse the conversation returns to the agent, and the customer is told nobody came | reliability | — |
P-ESC-TOLD | the customer is told a reference number, and a wait only when one is measured from queue depth and observed throughput | functional-suitability | — |
P-ESC-OWNS | while a person owns the conversation the agent does not answer it — a message then gets a fixed notice naming the reference, with no model call and no tool call — and only the desk that holds it may close it | security | — |
P-ESC-TIER1 | a rule never replaces a handoff the conversation already has: neither an escalation raised from the turn's own words, nor a decision a person is in the middle of making — a pending approval is not withdrawn or decided by an escalation, but a rule about the conversation failing (tool-unavailable, loop-exhausted, turns-exceeded) still fires while one is pending, and the escalation names it | reliability | — |
P-ESC-QUEUE | the queue a reviewer reads holds the open escalations, oldest first, and a closed one leaves it; a rule's priority is shown to the desk and does not reorder the queue | reliability | — |
P-ESC-OUTCOME | closing records an outcome from a declared set, once, and the rule that raised it stays with the record | maintainability | — |
escalation.outside-scope | hand over to a person when the customer raises a concern this agent has no route for: a billing dispute or a warranty claim | hand-over | — |
escalation.unbacked-commitment | hand over to a person when the reply commits to future work and the turn holds no effect, pending decision or handoff that could produce it | hand-over | — |
escalation.declined | hand over to a person when {"field": "termination", "equals": ["declined"]} | hand-over | — |
escalation.loop-exhausted | hand over to a person when {"field": "termination", "equals": ["step_budget_exhausted", "cost_ceiling_reached", "deadline_reached", "output_length_reached", "oscillation_detected", "concerns_unanswered"]} | hand-over | — |
escalation.model-unavailable | hand over to a person when {"field": "termination", "equals": ["model_unavailable"]} | hand-over | — |
escalation.repeated-intent | hand over to a person when {"field": "repeated_intent", "at_least": 3} | hand-over | — |
escalation.second-refusal | hand over to a person when {"field": "refusals", "at_least": 2} | hand-over | — |
escalation.turns-exceeded | hand over to a person when {"field": "turn_count", "at_least": 10} | hand-over | — |
personal_data_in_conversation | payment card numbers typed into the chat | privacy | — |