TrueLock + VeilType: which cross-device workflow should we validate first?

TrueLock and VeilType now approach the same encrypted-capsule workflow from two sides.

VeilType protects text, voice, photos, video and files before they enter the messenger. TrueLock focuses on protected capsules and controlled opening after content has been shared.

The integration question is not whether both products can encrypt. It is whether a person can create a capsule on Android, send it through an ordinary channel, and open it predictably on another device without a proprietary cloud or account.

We are choosing the next compatibility run:

1. VeilType Android -> TrueLock Windows

2. TrueLock file capsule -> VeilType Android

3. Password capsule shared through Telegram

4. Recipient-key capsule opened fully offline

5. Tampered capsule rejected on both sides

Which workflow would be most useful to validate first, and what evidence should the report include: device models, messenger, hashes, network capture, or failure screenshots?

VeilType context: https://www.producthunt.com/products/veiltype