OWNER PILOTCONTROLLED PUBLISHING

Mesh Dispatch

One approved 3D-product release package becomes provider-specific work with explicit readiness, durable history, duplicate controls, and a visible safe stop when an outcome cannot be proven.

The recurring work

One repeated problem, made inspectable.

The same 3D product must be expressed through different marketplace rules, prices, licenses, categories, tags, and media formats without losing approvals or repeating an uncertain action.

What the system handles

Owner-selected release-package intake and preflight
Destination-specific asset and metadata plans
Durable destination history and replay-resistant receipts
Bounded reconciliation with Resolve & Resume after a safe stop

What remains human

Authority stays visible.

The owner chooses the package and destinations, reviews release facts, and handles account selection, login, MFA, CAPTCHA, provider terms, and uncertain outcomes.

Operating mode

Hybrid

Owner pilot · provider-sensitive execution

Structured release plans and replay controls surround provider-specific work; uncertain or exhausted outcomes stop visibly for owner reconciliation.

What has actually passed

Current UI evidence shows separate destinations, durable history, and an UnsafeToContinue owner stop; read-only public Thangs and YouTube pages show channel-specific presentation examples.

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

The hero is an Evaluation 0.1 build with simulated connectors. Public listings are read-only evidence and do not prove that the captured session created them.

Mesh Dispatch desktop workspace with Cults3D, YouTube, and Thangs destinations, package preflight, stopped watch status, and release history. — The Evaluation 0.1 workspace uses simulated connectors and separates destinations, run mode, preflight, activity, history, and items requiring attention.Open full-size image

Mesh Dispatch Needs Attention window for a blocked Thangs release, showing completed Cults and YouTube destinations, required reconciliation, UnsafeToContinue, and Resolve and Resume. — When bounded Thangs recovery is exhausted, Mesh Dispatch preserves completed destinations and stops as UnsafeToContinue until the owner reconciles the outcome.Open full-size image

Public Thangs listing for the Tunguska Meteorite Containment Cradle with product images, EntropyArchives seller identity, price, and license notice. — An owner-controlled public Thangs page shows the model, seller identity, price, category, and restricted-license treatment; it is read-only evidence, not proof that this capture session created it.Open full-size image

Connection setup keeps provider identity and authorization boundaries explicit, including a dedicated Thangs profile and re-verification before publishing.Open full-size image

Public Thangs page for a volcanic Ganesha model with gallery images, EntropyArchives identity, subscription access, and a five-dollar purchase option. — The public Thangs page presents the Ganesha model through subscription and one-time purchase choices with a restricted-license notice.Open full-size image

Public YouTube Short showing a rotating volcanic Ganesha model from the SparkAndSpoolCo channel. — The same public model is presented as a YouTube Short, showing a channel-specific format rather than one generic listing.Open full-size image

Current limitations

Proof has a boundary.

The active Sea Dragon Thangs release did not reach final Save and has no verified public URL or receipt. Universal marketplace support, fully unattended publishing, perfect provider recovery, and current Cults visual verification are not observed.

Pattern this could support elsewhere

A starting pattern, never a promise.

A controlled multi-destination publishing pattern that preserves completed work, prevents blind replay, and asks for owner reconciliation when a provider outcome is uncertain.

START WITH THE WORK

Bring one recurring workflow.

Launch your first AI workflow