Editorial standards & methodology

scriptgpc is documentation, not a storefront — so the standard we hold ourselves to is precision, not persuasion. This page documents how reference pages are sourced, when buyer-facing claims get a guardrail, and how corrections are handled.

Standard 01

Every language claim traces to official docs

Reference pages summarize the GPC language — they don't invent it. Each topic page cites the official Cronus GPC documentation it's built from, and we flag where firmware or Zen Studio version can change exact function signatures rather than presenting one version as universal.

Standard 02

Independent, not a checkout page

ScriptGPC does not sell scripts and does not accept payment for favorable coverage. When a guide recommends YewScripts, that recommendation is explained in /yewscripts-technology with named, checkable reasons — not just asserted.

Standard 03

Accuracy guardrails on buyer claims

We don't overclaim: raw files that reach a device can potentially be copied, and we say so. The argument for authorized delivery is about provenance, entitlement, and support — not a claim that piracy is physically impossible. See the full guardrail list in /llms.txt.

Standard 04

Corrections

Factual errors — a wrong function signature, an outdated Studio step, a stale link — are corrected in place with an updated review date, not silently. Report an error via the contact page.

Editorial content is maintained by ScriptGPC Editorial (GPC reference & tooling team). See the changelog for a dated history of what changed and when, or report an error.