GOAT.CX editorial policy:
sources, AI and corrections.

This policy explains the evidence hierarchy, automated assistance, correction process, market-data handling, and limits applied across GOAT.CX.

A staircase of illuminated glass platforms, brightest at the base, representing a tiered evidence hierarchy
A staircase of illuminated glass platforms, brightest at the base, representing a tiered evidence hierarchy. Original GOAT.CX editorial artwork.

How the GOAT.CX editorial policy classifies claims

Technical claims

These should resolve to an on-chain record, protocol document, or named data provider.

Historical claims

These should resolve to a dated archive, direct project material, or attributable reporting.

Interpretive claims

These are labeled as analysis. They are not presented as ledger facts.

Prefer the closest available evidence

Evidence order

  1. Direct records: on-chain data, transaction records, and dated archives.
  2. Primary documentation: protocol documents and direct project statements.
  3. Independent context: attributable reporting and established data directories.
  4. Community material: useful for reception and lore, but not proof of a technical or financial claim.

Timestamp changing market data

Current GOAT observations name the provider and freshness state. Price uses the deepest-liquidity pool returned by the live feed; aggregates may span multiple discovered pools. Historical charts identify their provider and period. A displayed observation is not an executable quote. Review the live-data methodology

Disclose how automated systems assist

Automation may assist with data retrieval, drafting, internal consistency tests, structured-data generation, and original visual production. It does not create first-hand experience, professional credentials, or a basis for unsourced certainty. Material factual claims remain attached to named evidence, and original AI-assisted illustrations are labeled.

A named human approves scheduled dispatches

An automated import cannot publish itself into search. Each scheduled dispatch must carry explicit approval from a named reviewer, a review date, at least one inspectable external source, and a specific explanation of what the page adds beyond existing coverage. The publication gate checks developed sections, internal context, heading structure, unnatural repetition, and overlap with earlier dispatches. A page that fails stays outside the index and sitemap until it is reviewed.

Usefulness decides length and freshness

GOAT.CX does not pad a page to an arbitrary word count. A short answer can be complete, while a complex claim may need a longer source trail. A date changes only after a substantive public update; a new publication date is never used to make unchanged material appear fresh.

Correct the record without hiding the route

Substantive updates change the visible modified date and sitemap signal. Corrections should preserve the page URL when the subject remains the same. Source challenges, rights concerns, and factual corrections can be sent to [email protected].

How GOAT.CX is funded and what that excludes

GOAT.CX does not sell coverage, paid placement, sponsored articles, press-release republication, or ranking positions in any list. No entity pays to appear in the evidence ledger, the research library, or the market pages, and no external party reviews a draft before publication.

The publication does not issue, market, or hold a position it promotes to readers. External links support verification and never carry affiliate or referral tracking. If a commercial relationship ever changes that rule, it must be disclosed on the page carrying it rather than hidden in a site-wide notice.

No rented sections or third-party authority

The dispatch pipeline is a production tool controlled by the GOAT.CX Editorial Desk, not an open publishing platform. Outside businesses cannot place unrelated pages on this domain to inherit its search signals. Every indexable page remains within the stated editorial scope and under the same sourcing, review, correction, and removal standards.

What this policy cannot promise

An address is not a verified person

On-chain observations show what a node reported at a moment in time. They cannot prove a person's identity, a custody agreement, or an asset's safety. Holder figures list addresses, not beneficial owners. One address may represent an exchange, pool, program, or many customers.

A live number can still be incomplete

Market values can be delayed or wrong when a provider fails. Historical ranges only cover the period a provider returns. If the public record cannot settle deployer identity or key custody, the answer stays unproven until better evidence appears. See the desk's stated limits.

No promise of returns or individualized advice

GOAT.CX does not present attention, market capitalization, or past highs as a valuation floor. GOAT can lose most or all of its value. Readers are expected to verify the mint, understand the transaction, and make their own decisions. Use the GOAT risk guide

Who is responsible for this policy?

The organizational GOAT.CX Editorial Desk applies this policy. The broader mission and domain-preservation position are available on About GOAT.CX