Source and review method
How PodInk keeps podcast posts grounded in sources
PodInk keeps podcast content repurposing grounded in two distinct inputs: the episode passage and, when supplied, the listener’s own reaction.
AI can organize those inputs into a reviewable main draft, but AI wording is not treated as a source. The listener verifies the evidence, approves the point, reviews each platform version, and decides whether to publish.
- Source
- A podcast passage, speaker, and playback position
- Viewpoint
- The listener’s optional text or voice reaction
- AI role
- Organize material and prepare drafts for review
- Human role
- Verify, edit, approve, and initiate publishing
Published by PodInk · Reviewed by PodInk · Published and updated
The five-step method
Each handoff has a different job. Keeping them separate makes the final claim easier to inspect.
- Capture a reaction. Save text or record up to 60 seconds of voice at the relevant listening position. A reaction is optional when the goal is a clearly labeled source summary.
- Locate the surrounding passage. Keep the speaker and timestamp attached so the excerpt can be reopened and read in context.
- Separate source from viewpoint. Label what the speaker said, what the listener thinks, and what AI merely reorganized. Do not silently merge those roles.
- Approve one main draft. Resolve unsupported claims and important conditions before creating a platform version.
- Review each output separately. X and LinkedIn use different structures, but both remain connected to the same approved point. The user initiates publishing.
What stays visible
The prepared workflow is designed so a reviewer can trace the final wording back through each decision.
- User input
- Reaction captured at 12:40.
- Evidence
- Supporting passage at 31:18.
- Condition
- Qualifying passage at 1:18:10.
- Confirmed core
- Main draft, version 3, approved by the listener-editor.
- Separate outputs
- X review and LinkedIn review remain independent.
You can reproduce this exact example in the viewpoint scanner, continue through the prepared source notes, and inspect both platform forms in the platform adapter.
Failure cases and limits
A source trail reduces ambiguity; it does not remove the need for judgment or repair every weak input.
| Failure case | Required response |
|---|---|
| The transcript mishears a name, number, or quotation. | Reopen the source, correct it, or avoid the claim. |
| The passage does not support the listener’s conclusion. | Narrow the point, find better evidence, or remove it. |
| No personal viewpoint was supplied. | Label the result as a source summary, not a personal take. |
| Publishing status cannot be confirmed. | Pause and check the platform before trying again. |
PodInk does not promise perfect transcripts, factual correctness, automatic publishing, audience growth, or virality. The method is a review system: it makes the source, transformations, and human decisions inspectable.
Before a draft is ready
The final review asks whether the wording is supported and whether it still belongs to the person publishing it.
- Can every factual claim be traced? Keep the episode, speaker, and timestamp close enough to reopen.
- Are quotation marks earned? If wording was paraphrased, present it as a paraphrase rather than a quote.
- Is the viewpoint owned? Separate the listener’s judgment from the source speaker’s position.
- Did platform shaping change the point? Compare each X or LinkedIn version with the approved main draft.