Publishing policy

Evidence before publication.

Our standard for technical guides, reviews, corrections, and AI-assisted work.

Authorship and review

GS Copilot posts identify an author. Technical articles that claim a tested outcome must also record a substantive reviewer, test date, runtime, required scopes, expected output, failure cases, and official source links.

Testing and sources

We test code in the stated Apps Script runtime before publishing it. Guides include complete code and setup notes where relevant. We cite primary Google documentation for platform behavior and link sources in the article.

Corrections and AI assistance

AI may assist with drafting, editing, or code exploration, but a named human remains responsible for the published result. Send corrections to support@gscopilot.com. Material corrections update the article review date and its visible evidence.

Discovery surfaces

Posts marked for rewrite or without completed evidence stay out of the sitemap, feed, blog listings, and machine-readable content until review is complete.