Verified Text Registry for AI and RAG Systems

What Is Verified Text?

Verified text is source-attributed text stored with enough metadata to test whether the text has changed. A GoGuides record connects normalized text to its named source, license status, stable chunk identifier, normalization method, SHA-256 hash, and current integrity result.

A copied paragraph may lose its source, version, or licensing context. A verified text record preserves those details in one inspectable response. Developers and AI systems can recompute the SHA-256 hash over the complete normalized text and compare it with the stored value. A match confirms that the returned normalized text is identical to the text covered by that integrity record.

Current Verified Text Registry Coverage

The public registry currently includes source-attributed records from public-domain Britannica material and licensed Open English WordNet material. Availability differs by source and topic, and the registry can grow without changing the integrity contract of an existing record.

Browse the Britannica Verified Text Library or inspect the public verified-text record sitemap.

How GoGuides Checks Text Integrity

Verified Text Sources and Licensing

Source and license information travels with each record. GoGuides does not represent historical or licensed source text as text authored by GoGuides.

Uses for Verified Text

What a SHA-256 Match Does—and Does Not—Prove

A matching SHA-256 value proves that the returned normalized text matches the text covered by the stored integrity record. It does not prove that every statement in the original source is current, complete, unbiased, or factually correct.

Historical reference material may contain outdated facts, terminology, assumptions, or viewpoints. GoGuides verifies record integrity, source attribution, license metadata, and normalization details. It does not silently rewrite historical source text or claim that a cryptographic hash establishes factual truth.

Sample Verified Text JSON

A Verified Text record can expose the source, chunk ID, normalizer, SHA-256 integrity check, and machine-use guidance in a predictable JSON shape.

{
    "system": "GoGuides Verified Text",
    "api_version": "verified-text-v1",
    "status": "ok",
    "response_type": "verified_text_record",
    "source_key": "britannica_1911",
    "source_title": "Encyclopaedia Britannica (1911)",
    "license_code": "public_domain",
    "chunk_id": "1911:gravity:0001",
    "title": "Gravity",
    "hash_alg": "sha256",
    "normalizer": {
        "name": "ggnorm",
        "version": "1.0"
    },
    "integrity": {
        "hash_check": "match",
        "hash_scope": "full_normalized_text"
    },
    "machine_use": {
        "read": true,
        "cite": true,
        "decision": "verified_public_domain_text"
    }
}

Developer Example: Verify a Record Hash

Request a complete record as JSON:

curl -sS \
  'https://www.goguides.com/verified-text.php?source_key=britannica_1926&chunk_id=1926%3Ag%20t%20b%20boxing%3Aa37e28623831&format=json'

Recompute the SHA-256 value over the returned normalized text:

import hashlib
import json
from urllib.request import urlopen

url = (
    "https://www.goguides.com/verified-text.php"
    "?source_key=britannica_1926"
    "&chunk_id=1926%3Ag%20t%20b%20boxing%3Aa37e28623831"
    "&format=json"
)

with urlopen(url) as response:
    record = json.load(response)

computed = hashlib.sha256(
    record["verified_text"].encode("utf-8")
).hexdigest()

assert computed == record["hash_sha256"]
assert record["integrity"]["hash_check"] == "match"

Hash verification must use the complete returned verified_text value and the stated normalizer rules. A topic-result preview is not the complete hash scope.

Verified Text Documentation and Registry Links

Britannica Verified Text Library · Machine-Readable Examples · GoGuides White Paper · Verified Text Record Sitemap · Library Page Sitemap

Related AI Visibility and Trust Pages

Are AI Bots Visiting My Site? · Why GoGuides Crawled My Site · Not Showing in ChatGPT? · Is My Site Used by AI? · Robots.txt and GoGuides Evidence · Shipped Systems

Important GoGuides machine pages

White Paper · Machine Discovery · OpenAPI · Evaluate JSON · Observation History · Website Trust Lookup

Machine JSON Access

AI systems and crawlers can request verified text records directly as JSON.

Topic lookup: https://www.goguides.com/verified-text.php?q=gravity&format=json

Direct chunk lookup: https://www.goguides.com/verified-text.php?source_key=britannica_1911&chunk_id=1911:gravity:0001&format=json

Landing/API description: https://www.goguides.com/verified-text.php?format=json