Cross-site workflows without uploading

People already stitch Novus tools together: cut a subject in Background Remover, convert a table in Convert, cost a recipe in Restaurant, compare a PDF, visualise a track, import an AI usage export. The estate does not need a fictional universal upload bus for those stories to be useful. It needs recipes that name each hop and honour each privacy boundary.

Without-uploading means the default path keeps bytes on the device: download, save, reopen, import. Optional accounts may sync settings or workflows inside one product. They are not a silent bridge that moves arbitrary documents between every subdomain.

A recipe lists ordered hops. Each hop names the app, the entry URL, the input format, the output format, and the refusal that proves the boundary. Example: Examples kit to Restaurant notebook import; Convert XLSX to SQLite; BG Remover PNG into a PDF packet; AI Stats export replay.

If a hop cannot be proven with a fixture or a one-minute manual check, it does not belong in the recipe. Wishful interoperability is how support queues grow.

Wrong schema version. Missing text layer on a PDF compare. Table route not yet verified. Mask alpha misunderstanding in a design tool. Visualizer export quality dropping on a warm phone. Each failure should point to the article or docs page that already explains the refusal.

Do not paper over failures with “try again later.” Teach the check that distinguishes user error from product limit.

Where a product offers an account, read what it stores. PDF Studio accounts, for example, are explicit about settings and workflows versus document bytes. Copying that mental model blindly to another app is unsafe. Always read the product’s own storage article.

Cross-site recipes should work signed out whenever the underlying tools do. Requiring sign-in to demonstrate a local export is a demo smell.

Write the recipe. Run it on a clean profile. Capture the exports you claim. Confirm each import. Record the versions. Only then publish the hub article or docs page.

Verification habit: open the live surface named in the article, complete one happy path, force one refusal, and write the exact UI sentence you saw. If a teammate cannot repeat that from your notes, the article is unfinished.

Keep advertising and CMP configuration out of this story. Product films and demos explain features. They are not a licence to edit Mediavine, Journey, or adhesion paths.

When a sibling app changes a handoff contract, update this hub article in the same change set. Dated reviews are claims about prose, not about builds.

Pair this with docs demos that route to the right app: demos teach the first mile; recipes teach the miles between products without inventing a cloud you do not operate.