GoGuides Roadmap — Machine Web Intelligence & Adoption

Primary product

The core GoGuides product is an independently observed web-intelligence and provenance layer. GoGuides crawls and measures the public web, preserves historical state, exposes structured records, identifies meaningful changes, and gives outside machines a controlled way to request intelligence for specific public URLs.

Core machine loop Discover and crawl → observe and preserve provenance → Evaluate → Web State → Change Intelligence → URL Request → outside machine use and measurable follow-through.

Core systems live now

Independent crawler and web-intelligence index: GoGuides can discover, fetch, score, store, and revisit public web resources independently.
Trust and provenance history: independently observed state is preserved over time rather than reduced to a single current score.
Evaluate → Web State → Change Intelligence: machines can move from a broad domain decision into stored current-state intelligence and then into historical change detection.
AI URL Request: POST /request-url lets an outside machine request existing intelligence for an exact public URL or ask the protected normal crawler pipeline to observe an unknown safe URL.
Web Bot Auth: RFC 9421 HTTP Message Signatures, cryptographic caller verification, replay protection, bounded key discovery, and identity separation are live on the URL Request interface.
Machine discovery and contracts: machine-use.json, OpenAPI 3.1, canonical semantics documents, and the public Data License provide a deterministic integration path.
Machine activity telemetry: GoGuides separates documentation discovery, malformed requests, internal tests, explicit API adoption, cryptographically verified identity, status polling, and truth-surface follow-through.

The complete implementation inventory has moved to Shipped Systems.

Adoption scoreboard

A capability being live is not the same thing as outside adoption. GoGuides now measures external use separately from internal tests, synthetic traffic, crawler activity, and machine-document discovery.

Baseline captured September 5, 2026

→

External explicit URL Request POSTs: 0

→

Successful external URL Request uses: 0

→

External requests creating new observations: 0

→

Cryptographically verified external requests: 0

External discovery of GoGuides machine documentation is tracked separately and is not counted as API adoption.

What will count as traction

☑

First successful external URL Request — a non-internal explicit POST returning a useful 200 or accepted 202 response.

☑

First external request that creates a new authoritative observation — proof that an outside request caused useful crawler work rather than merely reading an existing record.

☑

First cryptographically verified external caller — Web Bot Auth establishes machine identity rather than relying on a User-Agent claim.

☑

Repeat machine use — outside clients return, poll status, follow truth surfaces, and request additional URLs over time.

What we are doing now

1. Prove external machine demand

☑

Measure real outside URL Request usage without mixing it with internal tests or simple documentation discovery.

☑

Watch for repeat use, verified callers, status polling, truth-surface follow-through, and requests that create new authoritative observations.

2. Improve freshness efficiently

☑

Continue tightening discovery, recrawl scheduling, deduplication, cooldowns, error handling, and queue protection so useful freshness does not waste crawler capacity.

3. Make machine integration easier

☑

Keep the machine-use document, OpenAPI contract, request documentation, examples, and response semantics easy for developers and agents to consume.

☑

Add reference clients or framework integrations only where they reduce real adoption friction rather than becoming features for their own sake.

4. Strengthen attribution and telemetry

☑

Improve safe local attribution, adoption reporting, identity analysis, and usage-quality measurement while keeping claimed identity, network attribution, and cryptographic verification separate.

What comes next

Global change intelligence

☐

Extend per-domain Change Intelligence into useful cross-domain change-event feeds after current-state and recrawl behavior remain stable.

Higher-capacity historical access

☐

Bulk checks, deeper history, exports, watchlists, and higher-capacity machine access where real consumers demonstrate a need.

Broader observation coverage

☐

Expand language and source coverage only after queue controls, spam suppression, provenance safeguards, and recrawl economics remain healthy.

Usage-driven API expansion

☐

New machine interfaces should be driven by demonstrated customer or agent pain points rather than by the desire to increase the endpoint count.

Secondary and supporting systems

These systems can remain useful and continue operating without competing with the machine-intelligence layer for equal strategic priority.

Consumer search

Search remains a public interface to the independent index and a useful way to exercise relevance, quality, and trust systems. GoGuides is not making consumer search feature parity with major search engines the primary roadmap goal.

Verified Text

Verified Text remains a proof layer for source-attributed, hash-verifiable knowledge objects. Britannica and WordNet collections demonstrate that machinery; the collections themselves are not the primary GoGuides product.

Webmaster services

Live Index, Trust Signal, verification, and Bot Radar remain useful webmaster-facing services and an adjacent revenue layer. Payment does not alter independent AI Rank, evaluation, or crawl priority.

AI Marketing Skills Assessment

The assessment and certificate registry remain available as a separate secondary offering. They are not part of the core web-intelligence and provenance engineering roadmap.

Detailed implementation history

The previous long-form roadmap contained the detailed inventory of shipped systems. That material has been preserved rather than deleted.

View GoGuides Shipped Systems Browse the detailed archive of completed crawler, search, provenance, trust, machine-interface, Verified Text, Bot Radar, webmaster, and supporting capabilities.