Content & Editorial Policy
This page covers every standard Sphinnx applies to published articles: content rating, authorship, AI usage, conflict of interest disclosure, the submission and review process, and the technical markup and discoverability layer that wraps every piece.
1 · What Sphinnx publishes
Sphinnx publishes long-form analysis and case studies written by named authors who cite their primary sources, type their commentary directly, and sign their work. Every article carries a completed Express Interview, a public edit log, an age rating, an AI usage disclosure, and a conflict of interest statement.
Sphinnx does not publish opinion columns without evidence, anonymous submissions, press releases, sponsored content, or content that originates substantially from AI generation without meaningful human authorship.
2 · Content rating
Every article carries a content age rating using the Apple App Store age band system. The rating reflects the article's subject matter, not its reading difficulty.
| Band | Definition | Typical Sphinnx content |
|---|---|---|
| 4+ | No objectionable material. Suitable for all ages. | Business analysis, regulatory case studies, marketing commentary |
| 9+ | Infrequent or mild thematic content. May include basic commercial or legal themes. | Articles covering litigation, financial disputes, consumer harm |
| 12+ | Infrequent or mild mature content. May include moderately complex ethical themes. | Articles covering fraud, exploitation, systemic harm |
| 17+ | Frequent or intense mature content. Graphic descriptions, adult themes. | Not currently planned for Sphinnx |
Every published article must carry a rating badge, a content_rating field in its OKF file, a meta name="rating" tag in its HTML head, and a contentRating property in its JSON-LD block. A Made for Kids boolean must also be declared; Sphinnx content is not made for children.
3 · Author standards & accountability
Identity
All Sphinnx authors publish under their real name. Pseudonyms are not permitted. Authors are identified by a named profile page at sphinnx/ivan-artsimovich/ (or equivalent), a portrait photograph, and a verifiable external link (website or LinkedIn).
Author approval
Before an article is published, the named author reviews it in full and formally approves it. The approval is recorded in the article's byline with a timestamp and carried in the page's Schema.org markup via reviewedBy. Authors are accountable for the published text regardless of how it was produced.
Conflict of interest — see section 6
Authors are required to declare any professional, financial, or personal affiliation with parties named or discussed in their articles. See section 6 for the full rule and disclosure format.
4 · Express Interview
Every Sphinnx article includes an Express Interview: a set of questions answered by the author and published verbatim in the article body. Express Interview replies are the author's direct voice, unedited and unparaphrased.
- Replies are typed in full by the author without AI assistance of any kind.
- No copy-paste from external sources or AI outputs.
- Published verbatim and in full — no truncation, paraphrasing, or editing.
- The author's replies cannot be updated after publication. The interview is a signed, time-stamped record.
- If a reply contains an error of fact, a correction note is appended to the changelog; the original reply text is preserved.
The Express Interview integrity standard is declared in the article's HTML head (meta name="express-interview-integrity"), in the OKF file, and in the article's JSON-LD block. Each reply carries a per-reply integrity anchor linking to this policy page.
5 · AI usage policy
Permitted uses
AI tools may be used by Sphinnx authors for research, source discovery, structural outlining, and factual checking. Authors must evaluate and independently verify all AI-generated claims before incorporating them into an article.
Prohibited uses
AI tools may not be used to generate the article's prose, to write or assist Express Interview replies, or to produce conclusions the author has not independently reached and verified.
Every article must declare which AI tools were used, what they were used for, and a statement of human ownership over conclusions. The disclosure appears in three places: the article's HTML head (meta name="ai-tool"), the article's OKF file (ai_tools: block), and as a visible inline disclosure beneath the author byline.
If no AI tools were used, the disclosure reads: "No AI tools were used in the production of this article."
The AI Context Capsule (cc:ai)
Sphinnx articles carry a structured machine-readable metadata file called an AI Context Capsule, following the cc:ai standard. The capsule packages the article's identity, provenance, integrity markers, primary sources, and key claims into a portable format designed to be copied into an AI chat session.
The defining feature of cc:ai is its prompts: block — a set of AI interaction prompts written by the article's author at publication time, covering research, analysis, critique, summary, and debate intents. These prompts are available on the AI Context Capsule explained page and can be copied via the "AI Context Capsule" button in the article's read bar.
The cc:ai format is compatible with Schema.org (BlogPosting), Dublin Core, and the Sphinnx Open Knowledge Format. It is published under CC0 (public domain).
6 · Conflict of interest disclosure
Authors are obliged to disclose any professional, financial, or personal affiliation with any party named or discussed in their article that a reasonable reader might consider a conflict of interest. This includes but is not limited to:
- Employment, contracting, or consulting relationships with named companies or individuals.
- Financial interest (equity, debt, options, or other instruments) in named entities.
- Personal relationships with named individuals.
- Receipt of payment, gifts, or access from named entities in connection with the subject matter.
- Prior or ongoing legal, regulatory, or competitive disputes with named parties.
Disclosure format
The conflict of interest statement appears in every article beneath the author approval line, before the content rating row. It must be one of two forms:
Rich markup for COI
The conflict of interest status is recorded in three places: a meta name="sphinnx:conflict-of-interest" tag in the article's HTML head, a conditionsOfAccess property in the article's JSON-LD block, and a visible disclosure element in the article body with role="note" and itemprop="conditionsOfAccess".
7 · Submission & review process
How to submit
Submissions are accepted by email at i137@proton.me with the subject "Sphinnx submission". Include a brief description of the article, a draft or outline, and your author profile URL or LinkedIn.
Review steps
Every submission goes through the following steps before publication:
- Initial review — subject matter fit, primary source quality, author identity verification.
- Express Interview — 3–5 questions set by the Sphinnx editor and answered by the author in typed replies.
- Source verification — all cited sources checked for accuracy and linked to their originals.
- AI disclosure review — AI usage declared, cc:ai capsule prepared.
- Conflict of interest check — author completes and signs the COI disclosure.
- Content rating — rating assigned, checked against the App Store band definitions.
- Author approval — author reviews the final text in full and formally approves publication.
- Publication — article published with OKF file, cc:ai capsule, changelog, Schema.org markup, sitemap entry.
8 · Available disclosure types
The following disclosure types are standard on Sphinnx. Each appears in the article's visible body, HTML head, OKF file, and JSON-LD as applicable.
meta name="rating", OKF content_rating, and JSON-LD contentRating.
meta name="ai-tool", OKF ai_tools, and JSON-LD hasPart.
meta name="sphinnx:conflict-of-interest", and JSON-LD conditionsOfAccess.
meta name="express-interview-integrity".
9 · Rich markup & discoverability
Every Sphinnx article is published with a complete structured metadata layer applied consistently across all articles as sitewide policy.
Schema.org (JSON-LD)
Each article page includes a JSON-LD block of type BlogPosting covering: headline, description, url, datePublished, dateModified, author (Person with name, url, sameAs, jobTitle, email, worksFor), publisher (Organization), contentRating, isFamilyFriendly, audience (with suggestedMinAge), keywords, articleSection, and hasPart entries for AI tools used and the Express Interview QAPage.
HTML meta tags
Every article head includes the following tags as sitewide policy:
Open Knowledge Format (OKF)
Every article has an accompanying OKF file at sphinnx/okf/{author}/{date}-{slug}.md. The OKF file is a YAML front matter document covering all bibliographic, authorship, rating, AI, and Express Interview fields. It is the machine-readable source of truth for the article and the basis for the cc:ai capsule.
AI Context Capsule (cc:ai)
The cc:ai capsule extends the OKF file with a prompts: block and a system_note field designed for AI language model consumption. The cc:ai standard is compatible with Schema.org, Dublin Core, and OKF. See cc-ai.md for the full specification.
Sitemap
Every article has a sitemap entry at sphinnx/sitemap.xml using Sphinnx custom XML namespace fields (sphinnx:contentRating, sphinnx:expressInterview, sphinnx:aiToolsUsed, etc.) alongside standard loc, lastmod, changefreq, and priority fields.
Canonical URLs
Every article carries a link rel="canonical" tag and an og:url meta tag. Where the article is also published on the author's personal site, the Sphinnx URL is declared as the canonical and the personal site URL is included via itemprop="sameAs" on the published date link.
10 · Contact
For questions about this policy, correction requests, or submission enquiries: i137@proton.me
For the cc:ai standard: see AI Context Capsule explained or email the address above.
This policy was last updated 27 June 2026.