Version 1 built · Testing in progressCONTROLLED PUBLISHING

Mesh Dispatch

Prepares a 3D-product release for its intended destinations, organizing the files and product information in one workflow. Review and approval controls keep publication decisions with the owner and help prevent duplicate actions.

The recurring work

The work this system supports

A single 3D-product release must be prepared consistently for its intended destinations without repeating setup, losing approvals, or publishing twice.

What the system handles

Release-package intake and preflight
Destination-specific preparation
Run-once and continuous-watch modes
Duplicate-action prevention

What remains human

The decisions people keep

Package approval, consequential facts, destination authorization, and publish decisions remain owner-controlled.

How it works

Hybrid

Rules control the workflow while AI helps prepare information. People review consequential actions.

Evidence and test scope

Version 1.0.0 has a sealed release bundle and installed-app smoke proof. The image below documents earlier Windows 11 simulated-connector testing.

Founder-built operating proof, not a customer case study.

Four verified Mesh Dispatch Windows 11 smoke-test views showing first-run setup, run once, continuous watch, and duplicate prevention with simulated connectors. — Windows 11 smoke test, July 23, 2026. The interface visibly identifies Evaluation/Simulation 0.1 and simulated connectors; one ZIP-content approval edge case remains under review.

Current limitations

Testing continues. The earlier verified image simulates Cults3D, YouTube, and Thangs.com connectors and identifies a ZIP-content approval edge case under review. Separate 1.0.0 release proof covers Cults3D and Thangs.com product cases plus one nominated YouTube video. MyMiniFactory, Printables, additional supplied videos, and local Cults MP4 transfer remain outside demonstrated coverage. Publication remains owner-controlled; general availability is not claimed.

What this approach might inform

A similar need still requires its own scope.

This example is implementation evidence, not an available off-the-shelf product. A customer application would require its own requirements, permissions, validation, and commercial scope.

This pattern could support controlled multi-destination release preparation when each destination and consequential action is separately proven.

Start with the work

Discuss the work you want to improve.

Discuss your business