GoGuides White Paper: A Machine-Readable Trust Layer for AI Source Clearance

What the white paper explains

GoGuides is not an AI model. GoGuides is a live machine-readable trust layer designed to publish structured source-clearance signals for systems that consume the web at scale. Its public surfaces include the signal feed, evaluate endpoint, verification/history pages, and deterministic favicon trust marker.

The white paper explains why AI systems need more than raw content. A page can be readable without being appropriate for citation. A source can be useful for general context but not suitable for sensitive advice. A domain can be observed but unverified. A source can be commercial, stale, restricted, filtered, or not cleared for specific machine uses.

Key ideas covered

Live machine-readable endpoints

GoGuides exposes public machine-readable surfaces that can be inspected by crawlers, AI systems, search engines, and automated agents. These endpoints are designed to make source context visible before a system decides how to use a source.

Example evaluate response

A crawler can request a domain-level evaluation and receive structured fields that describe the source, its public trust state, and related machine-readable records.

GET /evaluate.php?domain=goguides.com&format=json

{
  "system": "GoGuides",
  "api_version": "evaluate-v3",
  "query_normalized": "goguides.com",
  "trust_id": "GG-0000000000",
  "trust_state": "observed",
  "public_eligible": true,
  "lookup_type": "domain",
  "verification": {
    "status": "known_or_verified",
    "method": "public_record"
  },
  "freshness": {
    "last_observed": "2026-05-16",
    "stability_window": "time_based_signal"
  },
  "records": {
    "signal_url": "https://goguides.com/signal.json",
    "verify_url": "https://goguides.com/verify.php?domain=goguides.com",
    "history_url": "https://goguides.com/history.php?domain=goguides.com"
  }
}

Example source-clearance block

The core idea is not that every source is automatically safe for every use. GoGuides separates different machine uses so an automated system can make a more careful decision.

{
  "machine_use": {
    "read": "allowed",
    "summarize": "allowed",
    "cite": "conditional",
    "recommend": "conditional",
    "transact": "not_cleared",
    "sensitive_advice": "not_cleared"
  },
  "reason": "Observed source with public trust context. Not automatically cleared for high-risk use."
}

Example verified-text record

The verified-text layer extends GoGuides beyond domain-level source context into specific, source-attributed records. This helps machines inspect licensing, attribution, preview limits, hash scope, and full-record URLs.

GET /verified-text.php?q=gravity&format=json

{
  "response_type": "topic_lookup",
  "topic": "gravity",
  "verified_text_preview": "Preview text returned for inspection...",
  "preview_truncated": true,
  "hash_scope": "verified_record",
  "source": {
    "source_key": "britannica_1911",
    "license": "public_domain",
    "attribution": "Encyclopaedia Britannica 1911"
  },
  "full_record_url": "https://goguides.com/verified-text.php?source_key=britannica_1911&chunk_id=1911:gravity:0001&format=json"
}

Frequently asked questions

Developer links

• Open the public signal feed
• View a live evaluate JSON example
• View a live verified-text JSON example
• View the GoGuides trust profile example
• Read the GoGuides roadmap

Verified Text Layer and Bot Search Update

GoGuides also includes a live verified-text endpoint for AI systems, bots, and developers that need source-attributed text records with clear licensing and integrity metadata. The endpoint supports topic lookup through /verified-text.php?q=gravity&format=json and direct full records through source_key plus chunk_id URLs.

View live verified-text JSON example

Topic lookup responses are preview-first. They can include response_type, verified_text_preview, preview length and truncation metadata, hash_scope, machine_use, source license, attribution, and a full_record_url pointing to the canonical full verified record.

Initial live sources include Encyclopaedia Britannica 1911, Encyclopaedia Britannica 1926, and Open English WordNet. Britannica records are labeled as public-domain text. Open English WordNet records are labeled as CC-BY-4.0 and include attribution plus license information in the API result.

This extends GoGuides from domain-level source clearance into hash-verifiable text records: domain trust helps answer whether a source is fit for use, while verified text helps answer whether a specific record is source-attributed, licensed, and integrity-checkable.

What GoGuides does not claim

The white paper is intentionally careful about what GoGuides does and does not claim. GoGuides does not certify truth, guarantee safety, replace professional review, or clear sources for autonomous transactions or sensitive advice by default.

Instead, GoGuides publishes observed trust signals, source-clearance decisions, policy status, verification context, and time-based signals that can help machines make better source-level decisions.

Why this matters

AI systems are becoming major consumers of web content. They read, summarize, classify, recommend, cite, and act on information from the open web. Without source-level context, machines are forced to rely on incomplete signals.

GoGuides is being built to provide a clearer layer: a practical source-clearance and trust-signal system that helps automated systems understand how a source should be used.

Read the full white paper

The full PDF provides the complete framework, including machine-use decision examples, source conditions, trust IDs, fingerprints, time-based trust signals, the public signal feed, the evaluate endpoint, the verified-text endpoint, the GoGuides favicon trust layer, production favicon example, automated verification, Sybil and bulk-abuse resistance, restricted source handling, and future direction.

Read the GoGuides White Paper