Two doors, one act
When a harness is Completed and verified, the Release destination offers two doors.
| Door | What it does | Undo |
|---|---|---|
| Release locally | Gives this knowledge a version on this machine. You can use it in SOCI Cockpit right away | Withdraw, while it is local only |
| Publish to your team | Ships that same release, under that same label, to everyone in the workspace | None |
Local release creates the version on this machine; team publication distributes that same version. Harness identity and version history are outside this privacy-reviewed crop.
The version is chosen at the first door and carried, unchanged, by the second. A release is immutable and can never be relabelled.
Choose a version label
| Rule | Detail |
|---|---|
| Required | A release cannot be created without one |
| Characters | Letters, digits, ., -, and _ only |
| First character | A letter, digit, -, or _. It cannot start with a dot |
| Maximum length | 128 characters |
The label becomes part of a storage path and of the distribution identifier, which is why the character set is narrow. 1.0.0 and 25.3.0.0 are both fine; 1.0.0+build5 is not.
Release locally
- 01
Finish the harness
The rail's Release destination opens only when the harness reads Completed and verified.
- 02
Open Release
Choose Release on the rail, or take the shortcut offered from the harness list.
- 03
Enter the version
Type the label you want this knowledge to carry forever.
- 04
Confirm the consent dialog
Read the consequence sentence and confirm. The bytes become immutable at this point.
The local release appears in the harness list under On this machine, wearing a Released badge, and is immediately available to ground a SOCI Cockpit session.
Publish to your team
Team publishing is not authorised by the desktop role alone. The workspace must be provisioned, the distribution capability must be enabled, and the server must authorise the member or an administrator. The current deployment permits SOCK Creator and Knowledge Custodian without a separate administrative role; a differently configured deployment can require an administrator.
- 01
Start from a local release
The team door reads the label from the local release rather than offering a new one.
- 02
Choose Publish to your team
MSOCK builds the release archive, records what it contains, and uploads it.
- 03
Follow the progress
Publishing a large harness moves a lot of data. Progress is reported step by step, and an interrupted publish can be retried without rebuilding from scratch.
- 04
Confirm the published version
The harness list shows the version under your team's published releases, with its distribution identifier.
Withdraw a release
A local release can be withdrawn. The bytes survive; the label returns and can be used again.
Withdrawal is destructive and asks you to type WITHDRAW to confirm.
Version history
A harness keeps its release lineage. You can see which versions exist, which are local only, which were published, and which are installed on this machine.
Because a release is immutable, an update is always a new version of the same harness rather than a change to an existing one.
Receive a published harness
Anyone in the workspace who can see the harness list can take a published version.
- 01
Find the published version
Published versions appear in the harness list alongside your own work.
- 02
Choose to download
The row says which it is before you click: activating a version already on this machine is a local action, while one you do not hold is a download that can be large.
- 03
Open it
A downloaded harness opens the same screens a builder sees — Sources, the stage tabs, Graph, Review, and Ask — read-only.
Use a release in SOCI Cockpit
A released or published harness is what grounds an agent session. See ground sessions in SOCK knowledge for how the selection works and what happens when you change it.
Troubleshooting
| Problem | What to check |
|---|---|
| The Release destination is closed | The harness is not yet Completed and verified; finish the stages first |
| The version is rejected | Check the character set, the first character, and the 128-character limit |
| Withdraw is unavailable | The version has been published to your team and cannot be withdrawn from this machine |
| A publish stopped part-way | Retry it; the archive is kept and the publish resumes rather than rebuilding |
| A download will not open | The bytes are checked on arrival — if the identity does not match what was requested, the install is refused rather than opened |
| Release actions are greyed out | Confirm your SOCK role; releasing requires SOCK Creator or SOCK Knowledge Custodian |
| Local release works but team publishing does not | Confirm workspace setup, the distribution capability, and the deployment's publishing policy |