Methodology
Last updated: 2026-05-05
AutoKaam is a small editorial operation. One editor, a transparent pipeline, and a hard rule against fabrication. Here is exactly how an article goes from source to published page.
Six-stage pipeline
1. Source identification
Each article begins with a primary source — vendor announcement, SEC filing, official press page, named analyst note, first-person LinkedIn / X / Reddit post by an operator, GitHub release notes, or a public conference recording. Articles without a documented primary source do not enter the writing pipeline. The source URL is captured in frontmatter (sourceUrl) and renders as the source-quote block on the article page.
2. Triangulation
Numbers (pricing, valuations, headcount, model context windows, benchmark scores) are cross-referenced against at least one second source — vendor pricing page + the specific announcement, or two independent operator reports. If sources disagree, both ranges are published and the disagreement is called out in the article body. Where the source itself is rumor or unverified, the article is tagged with a clear 'Unverified' kicker.
3. AI-assisted drafting (disclosed)
First-pass research scaffolds and structural edits use AI assistance — Claude Sonnet (Anthropic) for analytical writing, Cerebras Qwen-3 and Xiaomi MiMo for schema-anchored extraction, OpenRouter routing for fallback. AI is also used for headline punching (the 'sexup' pass) and em-dash stripping. The full AI rotation and per-script assignment is documented in the repository README. AI never replaces verification or final judgment — every article gets human review.
4. Human editorial review
Every article is read by Aditya Sharma (founder/editor) before publication. The review checks: factual accuracy against the cited primary source, internal consistency of numbers and claims, removal of fabrications (no invented quotes, no fake company names, no hallucinated benchmarks), source-quote attribution, and the four mandatory headline patterns (named loser, hard number, power verb, named subject).
5. Quality gate
An automated quality gate (scripts/seo/qa-gate-v1.md) enforces frontmatter completeness, ASCI-fabrication regex, em-dash count, and the operator-verdict frontmatter (sourceQuote, verdictBullets, keyNumber, namedStake). Articles that fail gate checks are moved to content/drafts/_rejected/ with a reason header. Articles that pass land in content/news/ or content/tutorials/ and ship on the next deploy.
6. Daily refresh + correction policy
Newsroom dispatches fire daily via the GitHub Actions cron (.github/workflows/daily-news.yml). Tutorials and tool entries are reviewed on a rolling 90-day cycle. Stale pricing, retired vendors, or superseded model versions are either updated with current data or retired from the index — we do not leave broken claims live. Factual corrections ship within 48 hours of a verified report and carry a visible 'Updated on' date.
What we do not do
- ✕We do not republish vendor press releases as 'news' without adding operator analysis.
- ✕We do not run anonymous personas. After the 2026-04-29 persona collapse, every byline is either Aditya Sharma (analytical) or AutoKaam Editorial (desk drops).
- ✕We do not invent operator quotes, testimonials, or named sources.
- ✕We do not publish AI-generated content without human editorial review — even for short FAQ entries or headlines.
- ✕We do not accept sponsored placements inside article bodies. AutoKaam is reader-funded via display ads only.
- ✕We do not rank tools based on advertising relationships. Comparison pages present feature, pricing, and procurement data without commercial bias.
- ✕We do not chase head-term SEO at the cost of editorial substance. Narrow, source-anchored coverage beats broad, generic guides.
Source-of-record
The repo behind AutoKaam is public: github.com/Declan142/autokaam. Every article's edit history, commit log, and sourcing pipeline lives there. The qa-gate script, content schema, and prompts are all open. If you need to audit a claim, the trail is open.
For article-level corrections, contact [email protected]. For author bibliography, see Aditya Sharma's profile. For the editorial standards layer, see the editorial policy.
Owner: Aditya Sharma · Contact: [email protected] · This methodology is reviewed quarterly and on every significant change to the publishing pipeline.