From raw capture
to a reviewed story.

Receive a finished package.

The development machine places finished capture packages on a configured NAS share. The application verifies package paths, file sizes and checksums before registering footage. It retains the originals.

Metadata carries feature descriptions, before/after relationships and sensitive-information flags. A flag requiring manual review remains a review requirement.

Show what changed.

Group relevant sources into an episode. Generate a timeline, preview and portrait variants. Revise sections, add captions and choose a thumbnail using the local workspace.

Illustrative structure: the problem → development work → before/after evidence → remaining limitations → next steps. The application does not establish that a feature works beyond the supplied evidence.

Approve the actual result.

Check the preview's picture, audio, captions and sensitive details. Apply redactions where needed. Review a rendered export rather than approving a source filename alone.

Approvals are tied to the current edit. Revising the timeline or publication metadata invalidates earlier approval or transfer consent where required.

Choose a platform workflow.

YouTube uses its official API after account authorization and platform eligibility checks. TikTok uses reviewed inbox transfer where access is available; the creator completes posting inside TikTok.

Dry-run is the default. It simulates publication states without sending a video. Manual portrait exports remain available when API access is unavailable.