Where the authoritative notes live
The download page shows what changed in the current release and lists older versions. Sign in and choose Download MSOCK from the bottom of the launcher. Your installed version is shown by the update pill in the application.
This page summarises the changes that affect how the product is used and documented. It is not a per-build changelog.
Documentation baseline
This documentation was rebuilt against the shipping product in September 2026. The previous published version carried a 30 July 2026 baseline and described the product under its former name.
The application version line at the time of this rebuild was 0.2.22, released 19 September 2026.
The product was renamed
Genesis is now MSOCK. The launcher is MSOCK Studio, and the three areas carry their full names:
| Former name | Current name |
|---|---|
| Genesis, Genesis Studio | MSOCK, MSOCK Studio |
| Cockpit, AIDLC Cockpit | SOCI Cockpit |
| Command Center | SOCM Command Center |
Launcher tiles no longer carry Alpha, Live, or Coming-soon status ribbons. Routes, stored data, file names, and API values are unchanged — only the visible names moved.
SOCK: the vocabulary changed
| Former word | Current word |
|---|---|
| Capture (the object) | Harness |
| Survey | Scan sources |
| Freeze sources | Lock the source list |
| Plan (a stage) | Extraction order, reviewed on the Extract tab |
| Discover & Infer | Synthesize |
| Seal / sealed | Verify and complete / Completed and verified |
| Unit | Task |
| Surface (a discovered thing) | Discovered item |
| KnownUnknowns | Known Unknowns |
The Plan stage no longer appears as a stage of its own: the order analysis runs inside Scan sources and is approved on the Extract tab.
SOCK: newly available
| Capability | What it is |
|---|---|
| Graph | Build and explore the connected estate — entities, classifications, capability summaries, and verified relationships. Previously documented as unavailable |
| Review | Ten counts running from what SOCK read to billable CKU consumption, with a worked example on each |
| CKU consumption | Connected Knowledge Units, computed from the committed graph |
| Release and publish | Give a harness a version locally, publish that version to the team, withdraw a local release, and see version history. Previously documented as unavailable |
| Downloaded harnesses | Read a teammate's published harness on your own machine — the same screens, read-only, including Ask |
| Asset Inventory | A generated asset report across 12 families and 127 asset types, with evidence excerpts and JSON export. Labelled as a preview feature |
| SOCK roles | SOCK Consumer, SOCK Creator, and SOCK Knowledge Custodian now gate who can write. The former distribution-admin framing no longer applies |
| SOCK Assistant | An in-product assistant bound to the harness you are looking at, reaching the engine through a closed action channel |
| Oracle connector | Alongside PostgreSQL and MongoDB. Jira and GitLab remain workflow integrations; Atlassian is not a SOCK connector in this release |
| Selectable SSL mode | PostgreSQL SSL mode is user-selectable; Oracle defaults to TLS |
| Driver prerequisite check | The connector reports whether the database driver is present on this machine |
SOCI Cockpit: newly available
| Capability | What it is |
|---|---|
| SOCK grounding | A selector naming which published harness grounds this workspace's sessions, with explicit activate-or-download actions. Previously documented as "no built-in integration" |
| Session binding | A session answers from the selection active when it started, for its whole life |
| Workspace artefacts | Browse and preview the workspace's artifacts/ folder without leaving the application |
| Converged chat | A redesigned chat experience with limited availability, off by default |
The model picker is Opus, Sonnet, and Haiku, defaulting to Sonnet; thinking effort runs Low to Max, defaulting to High. Codex is disabled and no longer appears.
Installation: requirements are now stated
Confirmed requirements that the previous documentation could not name:
- macOS 13 or later; Windows 10 version 1809 or later, or Windows 11, 64-bit; Ubuntu 22.04 LTS or 24.04 LTS.
- 8 GB memory (16 GB comfortable), 10 GB free disk, a 1024 × 700 screen.
- Python 3.12 specifically and Claude Code on a paid plan are prerequisites and are not in the installer bundle.
- Windows installers are Authenticode-signed under Intellect Design Arena Limited.
- A first-run prerequisite check reports Python, the engine, uv, Claude Code, its sign-in, disk space, and git, each with a fix.
Administration and monitoring
| Change | Detail |
|---|---|
| Workspace setup | A one-time desktop wizard that pulls the organ pack, writes the workspace profile, runs a setup session, publishes the line, and unlocks the modules |
| Legacy SOCK import | Bring an existing docs/ folder into a configured workspace and publish it |
| Add people | The invite dialog is now Add people, carries a SOCK Role field, offers directory suggestions, and updates an existing member rather than re-inviting them |
| Bulk add | Add several people from a .csv file, with a per-row outcome |
| Workspace admin | The toggle now reads Make workspace admin |
| Sign-in wording | Provider-agnostic; MSOCK no longer names a specific identity provider in this flow |
| Usage Telemetry | One monitoring surface at a single route, role-scoped on the server. The earlier CIO Monitoring route now redirects to it |
| Devices | A platform fleet view with platform, rendering, health, and error detail, plus on-demand diagnostics |
| Bug reports | A triage queue for in-product reports, enabled separately per enterprise |
Known limitations
- Certify and Sustain are not product stages, and there is no continuous refresh or drift detection.
- A locked source list and a created release are both permanent.
- A version published to the team cannot be withdrawn.
- SOCK and SOCI Cockpit are desktop-only.
- There is no supported public REST API, SDK, connector extension point, or desktop plugin surface.
- The standalone SOCI module remains registered but unavailable.
- The Add-On Market end-user portal is not available in this release.
Writing a release note
- 01
Outcome
State the user-visible result in one sentence.
- 02
Availability
Name the surface, role, feature state, and any rollout qualification.
- 03
What changed
Describe behaviour, not implementation internals.
- 04
What to do
Give the smallest action needed from users or administrators.
- 05
Known limits
Name the important boundaries and the recovery guidance.