Editorial Policy

1. Scope

This policy applies to every page published at qgi.dev except inbound marketing copy written directly on third-party platforms (LinkedIn post captions, conference abstracts, podcast summaries). Everything hosted on qgi.dev — product pages, blog posts, news, research, press room, and industries — follows the rules below.

2. Author Identification

Every editorial article carries a named author. For technical and research writing the default author is Dr. Sam Sammane, Co-Founder and Chief Scientist, who holds a PhD in formal verification from Université Joseph-Fourier-Grenoble I (2005) and 20 peer-reviewed publications. Articles co-authored with the broader team are attributed with a visible with credit.

Articles written by contributors inside QGI's engineering, research, or field teams are published under the contributor's name, not under the QGI corporate byline, so readers can verify the author's background.

3. Editorial Independence

QGI has its own cap table and multiple investors. No investor, customer, partner, or supplier holds editorial veto over what QGI publishes on qgi.dev. Sponsored content — if we ever run any — will be labelled unambiguously as sponsored at the top of the article, with the sponsor named.

QGI does not accept payment, gifts, or referral fees in exchange for editorial placement, benchmark inclusion, customer case-study selection, or citation.

4. Review Process

Before publication, every article is reviewed for:

• Technical accuracy: Claims about architecture, performance, licensing, hardware, or product status are checked against the engineering record by a second reviewer who did not write the draft.
• Citation: Any claim that can be sourced — peer-reviewed papers, live artifacts on HuggingFace / GitHub, named evaluations, public benchmarks — is linked to its source. Claims that cannot be sourced are either flagged as forward-looking or removed.
• Regulated-industry safety: Content that could be read as legal, medical, or regulatory advice is reviewed against the QGI Disclaimer and explicitly scoped to "informational, not advisory".
• Consistency: Named entities (QGI HQ, product status, partner relationships) are checked against the single source of truth in the site's configuration so facts match across pages.

5. Sourcing Standards

Preferred sources, in order:

1. Peer-reviewed publications from IEEE, ACM, Springer, or an equivalent venue.
2. Live QGI artifacts (Q-Prime model card on HuggingFace, QGI Enterprise Factory repos on GitHub, QGI Commercial Model License v1.0).
3. Named enterprise evaluations with an on-record statement from the customer CEO or equivalent.
4. Primary regulatory sources (CFPB, HIPAA, FINRA, EU AI Act) cited by section.
5. First-party reproducible benchmarks, with methodology documented on /research/benchmarks/.

Secondary sources (analyst reports, blog posts, unnamed industry surveys) are used only when a primary source does not exist, and are flagged as such in the surrounding copy.

6. AI-Assisted Drafting

QGI uses AI tools to draft, outline, and edit content. Every AI-assisted article is reviewed and revised end-to-end by a named human author, who takes editorial responsibility for the final text, every citation in it, and every claim of fact. We do not publish unedited AI output on qgi.dev.

7. Updates and Versioning

Time-sensitive pages (product status, news, benchmarks) carry a dateModified field in the page schema and a human-readable "Last updated" line. When a published article is substantively revised — not typo-corrected — we add a dated changelog line at the bottom so readers can see what changed and when.

Factual errors are handled under our Corrections Policy.

8. Reader and Researcher Rights

• The right to contact the named author of a page directly through the contact form.
• The right to request a correction through the Corrections page.
• The right to a written basis for any factual claim we publish that is challenged in writing.
• The right to know that AI retrievers citing QGI content are reading our canonical corpus at /llms.txt and /llms-full.txt.

9. Contact

Questions about this policy, or an editorial concern about a specific page: use the press & media contact form or email sam@qgi.dev.