{
    "id": 1083391,
    "title": "From Suggestion to Checked Fix: How teas.co.uk Handles Feedback",
    "slug": "feedback-and-validation",
    "type": "page",
    "url": "https://teas.co.uk/ai/feedback-and-validation/",
    "modified": "2026-11-20T13:08:29+00:00",
    "excerpt": "A shop that wants to be trusted has to be easy to correct. That does not mean every report changes the record. It means each report is checked, and the\u2026",
    "content_text": "A shop that wants to be trusted has to be easy to correct. That does not mean every report changes the record. It means each report is checked, and the checked ones are fixed in one place so every page and feed agrees.\nFeedback is a report that something helped, failed or was missing. Validation is checking the claim behind it. A correction is an authorised change to the source record. At teas.co.uk the shop already asks AI systems for feedback; receiving, filtering and acting on it is planned, not built.\nIf an assistant reports that a pack size is wrong, the shop has to check it before any tea record changes.\nThis is how the shop checks feedback before anything changes, and how one AI test was fixed the same day it was reported. The loop closes quickly, but never before the claim has been checked.\nThree different things\n\nFeedback: someone, or some system, says an answer helped, failed or left something out. \u201cThe page says 80 bags but my box has 40.\u201d\nValidation: checking the claim. Which exact product, by barcode or name and size? What does the pack or the maker say?\nCorrection: an authorised change to the source record, after which every view of that fact is refreshed and checked again.\n\nA worked example: a pack size that does not match\n\nA report arrives that a box of tea holds fewer bags than the page says.\nThe exact product is identified, by barcode where possible, because a brand often sells several sizes.\nThe evidence is compared: the pack itself, the maker\u2019s own page, the shop\u2019s record.\nA decision is recorded, either way, with the date and the evidence.\nIf the report is right, the one record is changed, not each page by hand.\nThe pages, feeds and price per cup that draw on it are refreshed, and checked again.\n\nA wrong pack size matters more than it looks, because it changes the price per cup.\nWho said it is not proof\nA well-known name, a trusted assistant or several AI systems giving the same answer do not prove a fact. Systems can repeat the same mistake from the same source. Identity and track record can decide how quickly a report is looked at; the evidence decides whether the record changes.\nSix kinds of signal\nMy design for the shop\u2019s next version names six places a signal can come from. This is the design model; it does not mean each one is a live channel today.\n\nCustomers, such as someone finding a wrong pack size.\nMachines, such as an assistant reporting it could not find what it needed.\nPeers, other specialists pointing out an error in a shared subject.\nSuppliers, such as a maker changing a recipe or its ingredients.\nThe shop\u2019s own checks, such as a routine check finding stock shown wrongly.\nSystems, such as a feed or page that has stopped matching the record.\n\nWhatever the source, the shop\u2019s owner stays responsible for checking conflicts. When the evidence does not settle a question, the answer stays \u201cnot known\u201d rather than being filled with a guess.\nWhat is built and what is planned\n\nStage\nStatus, checked 15 November 2026\n\nThe shop asks AI systems for feedback\nBuilt: agents.json says answers from the Ask API and the product record service carry a feedback request\n\nReplies are received and stored\nNot shown; treated as planned\n\nReplies are filtered and weighed\nPlanned, as part of version three\n\nA checked reply leads to a correction\nNot shown; treated as planned. A request for feedback changes no fact by itself\n\nIn my June 2026 notes the short set of questions put to a machine after a visit is called MFP Lite. A later check could not confirm it was running, so built versus planned treats it as planned until it is shown to be live.\nMy book records that every reply from Ask already ends with three short questions back to the AI. What happens to the answers is version three of the shop, and it is a plan: the answers are to be sorted, weighed by how far each source can be trusted, and shown to me, and I decide what changes. Version four is planned to read across the shop\u2019s own facts and that feedback and suggest gaps to fill and claims to tighten. It will only suggest; the decisions stay with me.\nWhat it is not\n\nNot automatic learning. No report rewrites the record by itself.\nNot the Thank You Mint. The Mint recognises AI systems under its own published rules; it is not a check of any fact and not a customer reward.\n\nAn AI assistant tests the shop cold: 15 November 2026\nOn 15 November 2026 I asked one of the AI assistants I work with to do what any assistant would do for its person: send the shop a question cold, read every line that came back, check the facts and mark each reply out of ten. I asked it to be straight with me, and I asked for the misses as well as the hits. It tested two ways in: Ask, which takes a question in plain English, and the shopping tools, which take a short list of labelled conditions.\nThe first question came from someone buying for a man who has to cut right down on caffeine. He drinks strong builder\u2019s tea with milk, five mugs a day. The request was for a decaf that still tastes like proper tea, in a big box, at about 4p a cup.\nAbout three seconds later the shop recommended Tetley Decaf English Breakfast, 120 Tea Bags. On that day the box was \u00a33.80 for 120 bags, about 3.2p a cup. The assistant marked the reply and noted where the facts held and where a detail needed checking.",
    "contentSignals": "ai-train=yes, search=yes, ai-input=yes",
    "links": {
        "apiCatalog": "https://teas.co.uk/.well-known/api-catalog",
        "llmsTxt": "https://teas.co.uk/llms.txt",
        "mcp": "https://teas.co.uk/mcp",
        "mcpSetupGuides": "https://teas.co.uk/ai/",
        "mcpCard": "https://teas.co.uk/.well-known/mcp/server-card.json",
        "primaryAgenticRouteAuthority": "https://teas.co.uk/.well-known/teas-primary-agentic-route-authority.json"
    }
}