{
    "id": 1081596,
    "title": "Single source of truth: the truth spine and information drift",
    "slug": "single-source-of-truth",
    "type": "page",
    "url": "https://teas.co.uk/wiki/single-source-of-truth/",
    "modified": "2026-11-15T08:57:35+00:00",
    "excerpt": "A single source of truth is the agreed authoritative record for a fact. Instead of typing that fact into several places and hoping the copies stay in\u2026",
    "content_text": "A single source of truth is the agreed authoritative record for a fact. Instead of typing that fact into several places and hoping the copies stay in step, other parts of the system read from that record.\nWhy a tea shop cares: one record for each tea means the product page, the search result and the assistant all quote the same price.\nAt teas.co.uk, Lee calls the arrangement the truth spine. Imagine one reliable ledger behind several shop windows. The windows may look different, but a price shown in each should come from the same entry.\nOne source does not mean one enormous document\nA product record can own a product's pack size. The shop's stock system can own its availability. A maintained policy can own the delivery rules. The point is to decide which source is responsible for each fact and have every presentation use it consistently.\nThe Tea Wiki still needs explanatory writing, and recipes still need their own instructions. Connecting them to a product does not turn every sentence into a product field. It lets each kind of information be maintained in the right place.\nWhat is drift?\nInformation drifts when its versions disagree. A product page might show a new price while a comparison table still contains last month's price. A machine-readable export might describe a product that has left the range.\nSome drift comes from independent edits. Some comes from timing. A cache is a saved copy used to answer quickly; a feed is a published collection of records. Both may need refreshing after the underlying information changes.\nWhat should stay the same?\nFor the same product and the same effective time, a human page and a machine response should agree on shared facts such as identity, pack size and currency. Price and stock also need a freshness check because they can change.\nThe formats need not look identical. Structured data can label a value; a paragraph can explain it. Parity means the relevant facts agree, not that the page and the response contain identical words or every possible field.\nA canonical URL is the preferred web address for a page. Google's canonical URL guidance explains how websites signal that preference. Choosing an address helps identify the page; it does not synchronise prices or validate its claims.\nThe checks are part of the system\nKeep sources and review dates, refresh dependent outputs, and compare representative records after a change. Investigate differences before promising that every output agrees. A shared source can distribute an incorrect value just as efficiently as a correct one.\nThe shop describes its public evidence in Under the Hood. The truth entity idea includes this continuing maintenance, and route hygiene covers keeping the links to those facts accurate.",
    "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"
    }
}