A brief without habit-form constraints
The writing brief says only who the article is for and what it should communicate. It does not prescribe a time, place, frequency, duration, item, or required action.
Each writing stage uses a fresh local AI subagent without the parent conversation. It receives only the input and JSON contract it needs, and may not inspect the website source, database, runtime configuration, or unrelated article jobs.
Research without interrupting the reading flow
The Korean writer may consult research papers and can include the sources that help readers explore the subject. Research is a writing resource, not an automated medical-evidence approval gate.
Generic legal or medical warnings are not inserted throughout the article. When a reference notice is genuinely useful, it is kept to one brief sentence before or after the article.
Korean first, then one language at a time
The system creates only Korean JSON first. Five independent ordinary internet readers in their teens through fifties react to that Korean draft as relaxed readers, not researchers or judges. Their comments are suggestions, never scores or pass/fail decisions.
After the Korean article is finalized, each target language is translated by a new local subagent, one language at a time. Korean and English are never generated together. Korean X and Threads copy is also created separately from the final Korean article alone.
Only people publish
Deterministic code checks that every finalized JSON file exists and that its schema, hash, and provenance link match. It does not call AI, judge sentences, or rewrite copy. A complete bundle enters the database as pending and is invisible to public readers.
An authenticated human operator is the only party that can approve or reject an article. Approval exposes that exact revision immediately. Rejection requires a reason, which is stored so a later isolated writing run can prepare a new Korean revision.
Durable revisions and accountability
Published URLs remain stable. Database revisions and every human decision are retained; approving a newer revision supersedes the previous public revision without erasing its history.
Epipherse remains accountable for the articles it chooses to publish and can trace each public version to its exact imported bundle and operator decision.