{
    "id": 1079463,
    "title": "Built Versus Planned: Saying Only What Works",
    "slug": "built-versus-planned",
    "type": "page",
    "url": "https://teas.co.uk/ai/built-versus-planned/",
    "modified": "2026-11-20T13:08:28+00:00",
    "excerpt": "Built versus planned is the honesty rule Lee Samuel Tucker applies to teas.co.uk and to everything he writes about it: a thing is described as built only if it is live and usable today, and everything else is called planned or being tested.",
    "content_text": "Built versus planned is the honesty rule I apply to teas.co.uk and to everything I write about it: a thing is described as built only if it is live and usable today, and everything else is called planned or being tested. The line is kept in the open, so a reader, a customer or an AI assistant can always tell a working feature from an intention.\nIt is easy to claim more than exists. A tea shop asking assistants to trust it has to be exact about what it can do today.\nWhat really works today is published separately from what is only planned. Version two is built. Later versions are planned.\nI treat this as the spine of the way I rebuilt teas.co.uk in 2026. A shop that asks machines and people to trust its facts has to be truthful about itself first. \u201cThe moment I let a plan sound like a fact, you should stop trusting me.\u201d\n\nA tea example: the AI basket\nSince 6 October 2026, an AI assistant can, with the customer\u2019s approval, search the teas.co.uk catalogue, compare teas and fill a basket through the shop\u2019s MCP server. The customer then pays on teas.co.uk. That is built, and anyone can use it.\nWhat an assistant cannot do is go further and act on the customer\u2019s behalf inside limits the customer has set. That is planned. The two sound similar in a headline, which is exactly why the rule exists: \u201can assistant can shop for you\u201d is true today in a limited sense. It would overstate things to suggest it can place the order or pay for you.\n\nHow it works: the version stack\nI describe teas.co.uk as a stack of versions, each needing the one below it.\n\nVersion\nWhat it is\nStatus\n\nVersion one\nThe first shop, November 2025 to May 2026\nReplaced by version two\n\nVersion two\nOne checked set of product facts read the same way by people, search engines and AI assistants, live since 10 May 2026\nBuilt\n\nVersion three, the nervous system\nCollects feedback from machines and people, filters the noise, weights each source by how far it is trusted, and shows the patterns to the owner, who decides whether anything changes\nPlanned\n\nVersion four, the intelligence layer\nReasons over the facts and the cleaned feedback to suggest gaps to fill and claims to tighten. It suggests; the owner decides\nPlanned\n\nVersion five, controlled action and the visual layer\nBounded action for the customer within limits they set, and a faithful video version of the specialist answering questions\nPlanned\n\nWhat sits under \u201cbuilt\u201d today includes structured data behind every product, the Tea Wiki of entries, the Ask API (which declares premium_intent_supported and asks callers for the full human request), and the MCP server.\nOne item shows the rule at work. My June 2026 description of the stack counted a short set of feedback questions, put to a machine after it has used the site, as built. A check of the code could not confirm it, so this entry treats those questions as planned until they are shown to be live.\nChecked again on 15 November 2026, that one question splits into four. Does the shop ask machines for feedback? Yes: agents.json says answers from the Ask API and from the product record service carry a feedback request. That much is built. Is anything set up to receive the replies, does anyone or anything read them, and can a reply lead to a corrected fact? A request on its own shows none of those, so they stay under version three, planned. A request for feedback changes no product fact by itself.\nHow the rule shows up in what teas.co.uk publishes\n\nUnder the Hood publishes what the shop can measure about machine and human visits, and says where the evidence stops. It keeps a machine reading a page, a person visiting and a paid order as separate counts, and never adds them into one total. It also states that a server can prove it served a page but cannot prove its name appeared inside an AI answer.\nThe unexplained is published too. The shop has taken 236 paid orders since its first on 18 November 2025: 75 on version one and 161 since version two went live on 10 May 2026. Of the version two orders, search engines brought 71 and ChatGPT links 5. For 47, the origin could not be traced, and the shop says so rather than assigning them to a cause.\nCorrections are dated, not quiet. Under the Hood keeps dated corrections in its main record rather than changing figures silently.\n\nWhat it is not\nNot a promise that planned parts will be built. Versions three to five are designs. Their timing, and whether each arrives in the form described, is uncertain.\nNot proof that the ideas work. A built feature shows that something exists and runs, not that my wider argument is right.\nNot a reason to hide gaps. A known fault is reported as a known fault. I argue that a source which can find and count its own loose ends is easier to trust than one which cannot.\n\nIn my words: what is inside a tea shop built for AI to read\nSixteen years in the motor trade taught me to look at how something is built before trusting it, so here is the build behind teas.co.uk in plain English, with what is live today kept apart from what is still planned.\nPick up two boxes of English Breakfast. One holds 80 tea bags and the other holds 240. The bigger box costs more, but which one is better value?\nOn teas.co.uk the product page works it out for you and shows the price per cup. An AI assistant reading the same product gets the same figure from the same place.\nThat is the whole build in miniature: one set of facts, read the same way by a person, a search engine and an assistant.",
    "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"
    }
}