How we publish — and what we won’t.

Authorship

Every piece is signed. Authors carry a verifiable Person entity with credentials, bio, and external profiles (employer, professional network, prior work). We do not publish unattributed content, and we do not publish synthetic content under invented names. Contributor pieces and engineered authored UGC carry the same standard as staff bylines.

Sourcing

Factual assertions carry a citation ID linked to a named source. Where the source is a study, the study’s methodology is summarized; where it is an interview, the interviewee is named and credentialed. Where it is first-party testing, the test protocol is documented and re-runnable. We do not cite AI-generated text as a source.

Editorial gates

Each piece passes (1) a structured-data check — the JSON-LD must validate against schema.org; (2) a sourcing check — every claim has a citation ID; (3) an authorship check — the Person entity is complete; (4) a performance check — Core Web Vitals on the rendered page hit our budget (CLS < 0.05, LCP < 2.5s, critical JS < 90 KB); (5) an editor sign-off recording who reviewed, when, and against which standards.

Corrections + freshness

Publications carry both a publish date and a last-reviewed date. After 180 days a piece gets a freshness review; if the underlying facts have moved, the piece is updated or retired. Material corrections are noted inline with a timestamp.

What we won’t do

We don’t syndicate identical content across multiple owned domains. We don’t accept anonymous user-generated content. We don’t publish AI-only drafts without a named human editor in the byline and the sign-off. We don’t run sponsored content without a disclosure entity in the structured data and visible in the byline area.

How to contact us

Tips, corrections, and partnership inquiries: eshan@angrydigital.com.