Evaluate
Authoritative GoGuides evaluation for supported root/domain and exact-URL scopes.
Build a stronger evidence layer for the open web
The GoGuides roadmap is about making public web evidence easier for machines and humans to inspect, compare, and use responsibly. The direction is simple: observe more clearly, preserve provenance, expose change honestly, make uncertainty explicit, and keep interpretation separate from downstream decisions.
The foundation already in public use
GoGuides already exposes a connected set of public evidence and analysis surfaces. The roadmap builds on these contracts rather than inventing a second product beside them.
Web State V3
Latest supported stored observation state with provenance and explicit availability limits.
Change Intelligence
Deterministic comparison of concrete stored observations, including explicit abstention states.
URL Request
An explicit attributed workflow for requesting intelligence on one public URL.
Claim Support
Bounded model-assisted analysis against a fixed stored source observation.
Content Relationships
Conservative stored-evidence comparison of two exact public URLs.
What GoGuides is strengthening
Broader evidence coverage
Expand the useful public evidence available for supported web sources while preserving clear scope, provenance, timestamps, and missing-data states.
Longitudinal depth
Make repeated observations more useful for understanding continuity, change, freshness, and historical context without rewriting earlier evidence.
Better exact-URL intelligence
Continue improving page-level evidence while keeping root/domain state and exact-page state distinct and consistently resolved.
Clearer machine contracts
Keep human documentation, machine discovery, OpenAPI, response metadata, and endpoint semantics aligned so consumers do not have to reverse-engineer the system.
More useful deterministic evidence
Prefer reproducible comparison and explicit abstention wherever mechanical evidence can answer a question without requiring a model judgment.
Bounded analysis where it adds value
Use model-assisted analysis only when its input, scope, version, and relationship to the underlying evidence can remain inspectable.
Authority Clearing Network
GoGuides operates a separate machine-action clearing service built around Current Delegated Authority State. It is designed for bounded authority that may be consumed across independent autonomous systems.
Current stage
ACN 1.1 is live and ready to use. The implemented protocol enforces conservation, atomic reservation, idempotency, delegation, revocation closure, reconciliation, exact-action binding, account isolation, credential scopes, and signed evidence.
Separate subsystem
ACN does not replace GoGuides web evidence, AI Rank, provenance, Bot Radar, Trust Records, or the existing public machine feeds.
Live adoption phase
Documentation, machine discovery, account onboarding, and the live API are publicly available for developer and machine adoption. ACN remains a separate subsystem from GoGuides web evidence.
Technical specification
Read the Authority Clearing Network Technical White Paper
.
Open the PDF edition
.
Design rules that do not change with the roadmap
| Rule | Meaning |
|---|---|
| Evidence stays distinguishable | Observed facts, deterministic comparisons, derived assessments, and model-assisted judgments are not silently blended together. |
| Scope stays explicit | A root/domain record and an exact-page record can legitimately differ; the same normalized scope should not receive conflicting GoGuides values from different interfaces. |
| History is preserved | New observations add context. They do not rewrite what GoGuides previously observed. |
| Unknown remains unknown | Observation gaps, insufficient history, unavailable evidence, and unsupported conclusions remain explicit uncertainty. |
| Consumers keep the final decision | Outside systems decide how to rank, cite, retrieve, recommend, transact, or abstain. |
| Payment does not purchase evidence meaning | Commercial participation does not buy a higher AI Rank, a favorable grade, or guaranteed outside-platform treatment. |
What belongs on the public roadmap
The public roadmap describes user-facing capabilities, evidence quality, interoperability, documentation, reliability, and the direction of the public product. Internal infrastructure, security controls, abuse defenses, private operating thresholds, and business planning are not part of the public product contract.
How to follow the product as it evolves
Use the Developer Hub for the current capability map, machine-use JSON for machine discovery, OpenAPI for the formal public contract, and the technical white paper for the architecture and evidence model.