ScribeClaw is an article-automation agent for "Jjom-Aneun Gijadeul", the Chosun Ilbo startup-interview column. Upload the interview recording and it produces a draft in the reporter's voice — but the point isn't speed. It's guaranteeing, through system design, the trust that "the interviewee's words are never changed."
Ordinary transcription and summary tools polish statements to sound "plausible," changing what was actually said. In an article, that's fatal.
Ordinary tools smooth quotes into distortions of the actual statement and fill ambiguous parts with arbitrary guesses. For journalism, which must never distort the interviewee's words, they were unusable.
For a 60-minute interview: 1–2 hours to transcribe, 1–3 hours to draft. On top of that, checking each quote against the source was done manually by a person.
Mishear a company name, product name, investment amount, or date and it becomes an article error. Numbers especially — "a wrong number is still a plausible number" — so text alone can't tell right from wrong.
Upload recording → company dictionary → transcription → selective correction → angle selection → article draft. It keeps running on the server even if you close the window, and hands off to the reporter whenever judgment is needed.
Pre-register proper nouns from press releases and IR.
Transcribe the recording by speaker.
The reporter reviews only the ambiguous cases.
Set the article's angle and structure.
A draft with quotes checked against the source.
Feed in the company's press releases and IR (links, PDFs, text) before the interview, and it gathers proper nouns and easily-misheard phrases in advance to use as the basis for transcription and correction.
It auto-corrects obvious transcription errors, but for anything ambiguous — and numbers and dates it never auto-corrects — it asks the reporter to confirm. It shows the original audio for that segment along with the surrounding context, so the reporter only has to choose accept, keep original, or hold.
It checks every quote in the draft against the source one by one, rewrites only the paragraphs that don't match, and re-verifies — repeating the loop on its own. It also detects and flags unsupported statements (fabricated facts).
Check each interview's progress and generation cost on a dashboard, and pick up work again anytime. It sets the angle first and reconstructs the material as an "article" rather than in interview time order.
Rules like no auto-correction of numbers and source-verification of quotes are nailed down as code contracts (L1–L7), so distortion can't get in to begin with.
This is a single-user PoC stage, so operational metrics (articles published, satisfaction) aren't in yet. Here is what's been confirmed so far.
Journalism principles like source-verification of quotes and no auto-correction of numbers are enforced as code contracts (L1–L7), making it structurally impossible for distortion to enter.
The gate-loop, reporter confirmation (HITL), and persistent work context all work, and it has processed several real interviews end to end to produce drafts (about $2.7–$22.6 per item). We're preparing stronger fact cross-verification and formal operation.
The core: a human-in-the-loop (HITL) runtime that doesn't lose context when the reporter steps away, and a verification loop that checks quotes against the source.