How posts on viralr.dev are produced

This page describes content production specifically for the viralr.dev account (the posts, threads, clips, and ad creative we publish under our own brand). It is an application of our broader Standards, the platform-wide commitment enforced on every account in the suite. If this page and Standards ever conflict, Standards wins.

What we guarantee

• Every post passes the automated quality gates described in /standards before publish: voice match, platform-native shape check, spam-score filter, zero invented specifics, exposure-manifest compliance.
• Platform signals (engagement, reply volume, ad click-through) feed back into topic selection. Every post is traceable to the signals that shaped it.
• We do not accept paid placements. Cross-platform shaping is editorial, scored by topical fit and voice continuity, never by payment.
• No behavioural tracking of readers, no third-party fingerprinting on the viralr.dev frontend, no data sold. We do not run ads to the readers of viralr.dev itself.
• Every post carries an AI-assisted disclosure where the platform requires one, and a visible link to its lineage audit trail.

What we are not

• Not an engagement farm. No ragebait, no fake testimonials, no fabricated customer quotes. The Builder-log engine checks commit SHAs against the real repo.
• Not a scraper. Research uses first-party platform APIs and public trend data. We do not clone, paraphrase, or repost third-party content without license.
• Not a content mill.Each post is uniquely generated for the platform's native form. The same angle gets a threaded hook on X, a narrative on LinkedIn, a single scroll-stop on Threads. No post is reused across accounts.
• Not opaque.Prompts, model versions, platform signals, validation gate results, and cross-platform shaping logs are all published on each post's lineage page.

What we do when we're wrong

Errors happen. When they do:

1. Report via heimlandr.io with the post URL and a description of the error.
2. We review within 72 hours. Confirmed errors on evergreen posts get a visible correction. Confirmed errors on time-sensitive platform posts are deleted and logged, since reply-chain corrections rarely reach the original audience.
3. If the error is systematic (stemming from a rule in our pipeline rather than one bad generation), the rule change and its public record go into the standards log.

Paid ads: additional disclosures

When viralr.dev runs paid ads via the viralr-ads engine:

• The ad is labelled per the platform's advertising standards. We do not run "native" ads that hide their commercial intent.
• Ad claims are passed through the same fact-check gate as organic posts. Unverifiable claims block the ad from going live.
• The targeting preferences we use (interests, lookalikes, retargeting lists) are public in our lineage pages. We do not buy third-party audience data.

Related

Content Policy v1.0 · Published 2026-04-22. If you believe a post contains an error, reach us at heimlandr.io.