Skip to content
GearDock

Documentation

Release and Export

The final two stages: marking content eligible to leave, and packaging it for a destination.

Last updated

Release marks approved content as eligible to leave GearDock. Export packages released content for a file download or a connected destination.

Release

Release is an explicit, per-item decision rather than a bulk toggle. It is the last point at which a change of mind costs nothing, and it re-confirms that the item genuinely passed review and claim checking rather than trusting that it must have.

Export

Export produces either a downloadable package or a delivery to a connected system. The release state is checked again at the moment the export runs, rather than being trusted from when the export was requested.

Why Re-Check at Export Time

Content can be withdrawn after approval. Re-checking at execution means a queued or retried export cannot carry out a decision that has since been reversed.

What Export Records

  • Which version of which product was exported.
  • Where it was sent, and when.
  • Who initiated it.
  • The result, including failures and retries.

That record is part of the product's history, so 'what did we send to that storefront, and when' remains answerable after the fact.

Something here unclear or out of date? Tell us Documentation gaps are worth more to us than feature requests.