Observe
GoGuides stores independently observed public web state and provenance for supported scopes.
Use GoGuides as an inspectable web-evidence layer
GoGuides gives AI systems, crawlers, search tools, monitoring platforms and data applications a public way to inspect web evidence without collapsing observation, interpretation and downstream decisions into one opaque score.
The machine-consumption model
Evaluate
Root/domain and exact-URL Evaluate expose the authoritative GoGuides assessment for the normalized scope.
Compare
Change Intelligence compares concrete stored observations deterministically and can abstain when the comparison contract cannot be satisfied.
Analyze
Bounded layers such as Claim Support and Content Relationships add analysis while remaining distinguishable from raw observation.
Monitor
History, Web State and change evidence let consumers decide when a source deserves renewed inspection.
Decide
The consuming system keeps control of ranking, citation, safety, eligibility, retrieval and recommendation policy.
Core public capabilities
| Capability | Use it for | Do not confuse it with |
|---|---|---|
| Evaluate | Authoritative GoGuides evaluation for a supported normalized domain/root or exact URL. | A universal source-truth certificate. |
| Batch Evaluate | Multiple evaluations through the same authority with batch transport. | A separate ranking or scoring system. |
| Web State V3 | Latest stored objective state for supported root-domain evidence. | A guaranteed synchronous fetch of the live site. |
| Change Intelligence | Deterministic stored-observation comparison. | A semantic claim about motive or materiality. |
| URL Request | Explicit attributed request for intelligence on one public URL. | Ordinary observational traffic. |
| Claim Support | Bounded model-assisted analysis against one fixed stored source observation. | A universal fact checker. |
| Content Relationships | Conservative exact-URL comparison using stored evidence. | Proof of ownership, coordination, intent or deception. |
Why the evidence classes stay separate
A crawler timestamp, text fingerprint, verification event, AI Rank, deterministic change
classification and model-assisted claim judgment are not the same kind of thing. GoGuides
keeps them distinguishable so a machine consumer can decide what weight — if any — each one deserves.
Efficient monitoring without blind trust
A consumer can use stable state, fingerprints, history and change evidence to avoid treating every request as a completely new source. That can support recrawl and reprocessing decisions, but GoGuides does not require a consumer to accept a cached conclusion after the underlying evidence changes.
Unchanged supported state
A consumer may decide that expensive downstream processing is unnecessary until relevant evidence changes.
Higher or changed state
A consumer can re-inspect the source or the affected evidence dimensions according to its own policy.
Observation gap
Unknown, insufficient-history and unavailable states should remain uncertainty rather than being silently converted to positive evidence.
Machine discovery is explicit
Start at /machine-use.json for capability discovery,
use /docs/openapi.yaml for the formal contract,
and use /developers for the human-readable map.
Boundary
GoGuides records can provide evidence and GoGuides-derived context. They do not force an
outside system to index, rank, cite, recommend, retrieve, transact, train on, or otherwise use a source.