Two different jobs
MSOCK uses the words source and integration for different purposes.
- A SOCK source contributes evidence to a harness. It is selected under Sources → Add source and becomes part of the locked, versioned boundary.
- A workflow integration connects SOCI Cockpit or SOCM Command Center to an external work system. It does not become SOCK evidence merely because it is connected.
Availability matrix
| Technology | SOCK source | SOCI Cockpit | SOCM Command Center | Direction |
|---|---|---|---|---|
| Local repositories and folders | Yes | — | — | Read-only into the harness |
| Knowledge artifacts | Yes | — | — | Read-only into the harness |
| Tacit knowledge | Yes | — | — | Authored in MSOCK, then locked into the harness |
| PostgreSQL | Yes | — | — | Read-only introspection and bounded samples |
| MongoDB | Yes | — | — | Read-only introspection and bounded samples |
| Oracle | Yes | — | — | Read-only introspection and bounded samples |
| Jira | No | Read and write through lifecycle commands | Read-only work-item context, Jira → MSOCK | Member-owned integration |
| GitLab | No | Read and write merge-request context | — | Member-owned integration |
| Confluence | Not available | — | — | No supported user entry point |
SOCK Add source tabs
The Add source dialog contains exactly four tabs: Local Repositories, Connect System, Knowledge Artifacts, and Add Tacit Knowledge. Connect System currently lists PostgreSQL, MongoDB, and Oracle.
Shared database guarantees
All three database connectors:
- run on the desktop using the signed-in member's own database credential;
- store secrets only in the operating-system credential store;
- pass credentials to the extraction process through standard input, not command-line arguments, environment variables, or logs;
- perform read-only introspection and write nothing back to the database;
- cap bounded reads at 10,000 rows and samples at 200 rows; and
- refuse a server below the supported version floor before writing harness files.
Choose the technology page in this section for supported versions, fields, TLS options, and scope behaviour.