What the Distribution tab manages

The workspace Distribution tab is the administrative view of knowledge and organ-pack versions available to a workspace. Each row identifies the line as MSOCK or Legacy and shows its version, status, stage, and creation time. It covers two different lines:

  • SOCK distributions — published knowledge harnesses consumed by SOCK and selected for SOCI grounding.
  • SOCI distributions — the versioned organ pack that supplies /ws- lifecycle commands.

Use this screen to inspect status and version before changing what the workspace receives.

The workspace Distribution table showing MSOCK lines, publication status, knowledge stage, and download actions with identifiers and publishers removed
Workspace distribution

The administrative table makes the distribution line, status, stage, and available action visible. Distribution identifiers, versions, dates, publishers, workspace, enterprise, and member identity are masked or excluded.

Actions

ActionPurposeCaution
DownloadRetrieve the selected distribution where the interface offers itLarge SOCK distributions can take time and disk space
RestoreReturn an eligible earlier or removed distribution to serviceConfirm the intended line and version before restoring
Purge nowRemove distribution material after a double confirmationDestructive; review active use and recovery options first
Release purge claimRelease the ownership claim around an in-progress purgeConfirm that no operator is still responsible for the operation
Republish organ packMake the current workspace command pack available againMembers may be prompted to fetch the newer pack

The exact action set depends on the line, its state, and the caller's administrative scope. Some actions require the MSOCK desktop application and are blocked from the web surface. A disabled action is preferable to guessing that a distribution is safe to alter.

Publishing authority

Publishing a SOCK harness begins in the desktop Release room, not the Distribution tab. Local release is available to a SOCK Creator or Knowledge Custodian. Team publishing additionally requires:

  • a provisioned workspace;
  • the distribution capability to be enabled; and
  • a server policy that authorises the member or an administrator.

In the current deployment, Creator and Knowledge Custodian can publish without a separate administrative role. Do not treat that as a guarantee for a differently configured deployment.

Verify a change

After a publish, restore, purge, or republish action:

1. Reload the Distribution tab. 2. Confirm the intended line, version, state, creation date, and publisher. 3. Check the corresponding member experience: harness availability for SOCK, grounding choices for SOCI, or installed commands for the organ pack. 4. If the states disagree, preserve the distribution identifier and displayed error for support.