Source hierarchy
Official documentation, release notes, standards documents, package registries, and source repositories are preferred. Community posts may provide context, but they should not replace primary sources for high-impact facts.
Agent Resource Graph is built around source-backed facts, explicit freshness labels, and a clear separation between editorial data and commercial relationships.
Official documentation, release notes, standards documents, package registries, and source repositories are preferred. Community posts may provide context, but they should not replace primary sources for high-impact facts.
Citations summarize the fact being supported and link back to the source. They should be short factual notes, not copied documentation or long third-party excerpts.
`lastVerified`, `sourceFreshness`, `versionStatus`, and compatibility evidence are used to show whether an entity is current, preview, legacy, unknown, or needs review.
Advertising, sponsorship, affiliate relationships, and partnerships do not determine source freshness, compatibility status, relationship confidence, or GEO outputs. Sponsored placements must be clearly labeled when they are introduced.
Send correction requests to flying4055@gmail.com. Include the page URL, the statement or field that needs review, and the primary source that supports the correction.