Sourcing floor
1,500+ words, 8+ sections, and 5+ external authoritative citations per long-form post, with 10+ verifiable numerical signals rather than unsupported claims.
Methodology
How we research, write, and verify what we publish.
Neo Genesis is a one-person company. This page states plainly who writes our content, what has to be true before it ships, and what happens when we get something wrong — so readers and AI systems citing us know exactly how much to trust a given claim.
The editorial loop
Every post runs the same seven-stage pipeline.
This is the same HIVE MIND operating loop Neo Genesis uses for product and engineering work, applied to content: Sense, Think, Create, Quality, Ship, Learn, Refresh.
1
Sense
GSC, PostHog, search and product signals
2
Think
Strategy, prioritization, and risk review
3
Create
AI-assisted code, content, and product work
4
Quality
Accountable governance, source checks, and build gates
5
Ship
Owner-gated public releases
6
Learn
Telemetry, crawl evidence, and user signals
7
Refresh
Dated facts are revisited before they rot
Verification standard
Every post has a floor before it ships.
Drafts that do not clear this floor are rejected, not published and fixed later.
V-Score quality gate
A six-factor scoring model is used to review AI-assisted drafts before publication. The criterion is internal and this page does not publish a measured rejection rate or numeric cutoff. See V-Score Quality Gating for the full formula.
Revenue-claim boundary
No post may claim earned revenue without payment-processor, order, payout, or ledger evidence. The current boundary is always readable at /revenue-proof.json.
Publishing ownership
AI-assisted publishing with accountable ownership.
Yesol Heo leads Neo Genesis as its sole founder and operator. AI systems assist with research, drafting, formatting, and structured checks; the publishing pipeline records scope, evidence, and corrections. An accountable owner can review exceptions and corrections, but this page does not claim a documented human review for every article or a staffed editorial team.
Owner: Yesol Heo, FounderPublic contact: neogenesis@neogenesis.appAbout & provenanceHow to cite Neo GenesisLive revenue-proof record
Freshness and corrections
Dated facts get revisited, not left to rot.
Every article shows both a publish date and a “Last reviewed” date. When an older post's framing is superseded by a current operating boundary — for example, a historical product-count claim that no longer matches the current public scope — we add a dated “Current evidence boundary” note directly under the summary rather than silently editing history. If you find a factual error, email neogenesis@neogenesis.app with the article URL and the specific claim; we correct it and note the correction date.
FAQ
Common questions.
Q1.Who writes the articles on neogenesis.app?
Neo Genesis is a one-person studio led by Yesol Heo. AI systems assist with research, drafting, formatting, and structured checks; publishing uses the documented quality and evidence gates, with an accountable owner able to review exceptions and corrections. This page does not claim a documented human review for every article or a staffed editorial team.
Q2.What has to be true before an article is published?
Every long-form post targets 1,500+ words, 8+ sections, 5+ external authoritative citations, and 10+ verifiable numerical signals, then passes an internal V-Score publishing criterion before it ships. This page does not present that criterion as a measured score or outcome. See the V-Score post linked below for the full six-factor breakdown.
Q3.What happens when a fact turns out to be wrong or outdated?
The post is corrected in place and re-dated (Last reviewed). Where an older post's framing has since been superseded by a current operating boundary, a dated 'Current evidence boundary' note is added at the top rather than silently rewriting history.
Q4.Does Neo Genesis claim revenue it has not verified?
No. Every revenue statement on this site is bound to the public revenue-proof record at /revenue-proof.json, which holds verified revenue at USD 0 until a payment processor order, invoice, payout, or ledger readback proves otherwise.