How the tool behaves
These are constraints the tool was built around, not features added afterwards. Each one rules something out, which is the point: a publishing tool is only trustworthy if the things it cannot do are as clear as the things it can.
Own accounts only
Clipping Publisher publishes exclusively to social accounts operated by Reku Media. It is not a service, there is no sign-up, and it manages no one else's accounts or data. Every connected account was authorized by its own owner signing in on the platform's consent screen.
A person approves every clip
Clips are never published as a side effect of the editing step. A publish job cannot be created for a clip that has not been approved by hand, and there is no configuration that relaxes this. When a reviewer rejects a clip, the reason is stored with it, so the record of why something was thrown out survives longer than the memory of it.
Runs locally
Source video, transcripts, rendered clips and the review database all stay on the operator's own machine. The only thing that ever leaves it is the finished clip that goes to the chosen platform, plus the caption text that accompanies it. There is no server component, no shared storage and no analytics collection.
Credentials stay in the system keychain
Access tokens and refresh tokens live in the operating system's keychain. They are not written to the project database, not committed to source control, and not printed to logs. Each token is used only to publish to the account that issued it — a token for one channel cannot be used to post to another.
One upload per approved clip
Publish jobs carry an idempotency key. An upload interrupted by a network failure resumes rather than starting a second post, and a job that has already produced a post cannot produce another. Failed jobs are retried a bounded number of times and then left in a failed state for a person to look at.
Licensed source material
Source video comes from material Reku Media is licensed to clip, under the terms set by whoever supplied it. Where a licence requires attribution or a mention, that requirement is recorded with the source and applied to every clip cut from it.
Rate and volume
Publishing is scheduled rather than bursty: jobs are spread across the day, one clip per account per slot, and the same clip is not posted to several accounts on the same platform. This is a deliberate limit on the tool, not a limit imposed by the platforms.