GoGuides Favicon Trust Marker

What the favicon is

Most favicons are decorative. The GoGuides favicon is functional: a small visual representation of a larger measured trust state. Its appearance is generated by GoGuides rather than supplied or styled by the site being measured.

• You do not upload it. GoGuides generates the marker from system data.
• You cannot buy its appearance. There are no cosmetic trust upgrades or pay-to-rank shortcuts.
• It is deterministic. The same resolved inputs produce the same visual result.
• It is inspectable. The visual marker can be checked against the deeper GoGuides record.

The favicon is the visual North Star

Full machine-readable records are useful when an AI system or developer needs detail. But the open web also benefits from tiny signals that can be fetched, cached, compared, and monitored cheaply.

That is the role of the GoGuides favicon. A change in rank, grade, trust state, timestamp, favicon seed, or other resolved trust inputs can produce a controlled visual change. That change can tell a human or machine that it may be time to inspect the deeper record.

One trust record, multiple public surfaces

The favicon is not a separate scoring system. It is one public surface of the larger GoGuides trust layer. The same underlying trust context is exposed in different forms depending on who or what is consuming it.

The favicon provides the compact signal. The deeper records explain what the signal means and why it changed.

What the visual parts can communicate

The favicon is intentionally compact, but its visual structure can carry several pieces of trust-state context. The exact rendering protocol can evolve while the underlying principle remains the same: the visual state comes from GoGuides data, not from a site's marketing claims.

Favicon caching and drift detection

Browsers, crawlers, CDNs, and intermediary systems commonly cache favicons. Because of that, GoGuides does not treat the image itself as the only source of truth.

For drift-sensitive monitoring, machines can compare deeper state such as:

• favicon seed
• broadcast fingerprint
• trust ID
• rank
• grade
• signal last changed
• time-based observation state

If the lightweight visual marker or fingerprint changes, a machine can request the deeper evaluate record to determine what changed.

Deterministic by design

Determinism is what makes the favicon useful as more than decoration. It gives the visual marker a repeatable relationship with the underlying trust state.

That relationship allows a browser, crawler, site owner, or monitoring system to compare what it sees now with what it saw before.

Verification: follow the marker back to the record

The favicon is designed to invite verification rather than demand blind trust. Anyone should be able to follow the visual signal back to the GoGuides record that gives it context.

• Use /verify for human-readable trust and verification context.
• Use /signal.json for the lightweight machine broadcast.
• Use /evaluate.php for the detailed machine-readable record.
• Use domain history to inspect how the observed state has evolved over time.

Harder to imitate meaningfully

Any public image can be copied. The defense is not pretending that copying is impossible. The defense is making the copied image independently checkable against a canonical GoGuides record.

• A copied favicon does not create a matching GoGuides trust record.
• A newly created domain cannot manufacture a long GoGuides observation history instantly.
• Changes in rank, trust state, timestamps, fingerprints, or favicon state can expose drift.
• Verification alone does not bypass GoGuides policy gates or automatically clear a source for higher-risk machine use.

The objective is not to claim that manipulation is impossible. The objective is to make trust state observable, structured, conservative, and difficult to fake quickly.

What the favicon does not mean

GoGuides deliberately separates observation, verification, citation clearance, recommendation, transactions, and sensitive advice.

• It does not certify that every statement on a website is true.
• It does not guarantee that a website is safe.
• It does not automatically clear a source for AI recommendation.
• It does not automatically clear autonomous transactions.
• It does not automatically clear medical, legal, financial, or other sensitive advice.

The favicon is a visual entry point into that larger source-clearance system — not a universal trusted/untrusted label.

FAQ

Can I upload or style the GoGuides favicon?

No. GoGuides generates the marker. Allowing sites to choose its appearance would defeat the purpose of a deterministic third-party signal.

Can I pay for a better-looking trust marker?

No. Activation or verification does not buy rank, bypass policy gates, or purchase a more favorable visual state.

What makes the favicon change?

Meaningful changes in the underlying resolved GoGuides trust state can change the marker. Depending on the current implementation, that can include rank, grade, trust state, time context, favicon seed, or related system state.

Does the favicon replace /signal.json or /evaluate.php?

No. The favicon is the lightweight visual monitoring surface. The machine-readable records remain the deeper source of trust context.

Where can the favicon be used?

It can appear within GoGuides surfaces and may also be requested or displayed by participating sites, browsers, crawlers, monitoring systems, and other machine consumers.

The principle

The GoGuides favicon is built around a simple idea: measured signals should be distinguishable from self-published claims.

A tiny public marker can reveal that GoGuides state exists, show when that state changes, and point anyone — human or machine — back to the deeper record.

The favicon is small by design. The trust record behind it is not. Read the GoGuides Machine-Readable Trust Layer white paper.