Skip to content

Labor · In-house development

Controllable knowledge work with k2a

k2a is our own development for accessing distributed knowledge bases. In closed trial, we are examining how machine suggestions stay verifiable and how different storage locations become reachable through one shared interface.

Isometric illustration: a folder, a review station, and a controlled handover form a compact tool chain.Isometric illustration: a folder, a review station, and a controlled handover form a compact tool chain.

Practical setup 01In-house development · closed trial

Releasing machine suggestions only after review

Machine-detected connections can be useful, but they must not become part of the reliable knowledge base without review. Suggestion, review, and confirmed knowledge need to stay clearly separated.

Language modelAllowlistSuggestionLockUnverifiedHiddenHUMANReviewConfirmedDiscardedFindableJournal

Classification In-house development · controlled suggestions in k2a One stop for review by humans: Review

How the setup works Allowlisting, status, and locks keep unreviewed suggestions separate from the approved knowledge base. Acceptance and rejection are recorded in the journal so they can be traced.
Scope and limitations

Not part of this demo: This shows the control path, not the quality, volume, or source of the machine suggestions.

The control mechanism shown is built and is being tested in k2a against our own holdings.

Practical setup 02In-house development · integrations still expanding

Reaching different storage locations with the same actions

Documents live locally, on company machines, or with storage services. Different access methods and operating models make a shared workflow difficult.

HUMANSelectionSelection listControl panelAddressRouterFolderRemote serverObject storageTransferTrash

Classification In-house development · shared access, integrations still expanding One stop by a human: Selection

How the setup works The address selects the matching access method. Behind it, different storage locations sit side by side as equals. System-specific functions stay tied to their own destination.
Scope and limitations

Not part of this demo: Not every planned storage type is connected yet. Deleting, restoring, and permissions differ by target system.

The shared access layer is tested. The scope and depth of the connections are being expanded step by step.

Closed trial with clear limits
k2a is not publicly available and is currently being tested only against our own holdings. The control and access paths shown are built. Scope, result quality, and supported storage types are still under development.

Back to the Labor overview →

Where does knowledge need to stay verifiable in your organization?

We look at one specific knowledge base together and determine which findings can apply automatically and which need confirmation by a human first.

Schedule a conversation