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.

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.

Test stand

Four machine suggestions are waiting for your review.

Knowledge network

Search the network

Pick a term.

Journal

  1. No decision yet.

Decisions are final. Start over resets the whole stand.

Visible to every search

3

accepted links

Unreviewed suggestions

4

stored, but hidden

In the journal

0

decisions with their source

Made-up sample network. The three states and their effect on search follow the control path in k2a. The suggestions are stored in the content and not generated by a model, two of them are wrong on purpose. The build makes no claim about the quality, volume, or source of real suggestions.

How the setup works Review four machine suggestions. Drag a card to the right and it becomes a solid link that every search sees. To the left, it stays in the journal only. Show suggestions to see what is stored but not yet reviewed.
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.

Test stand

Enter an address or pick a target.

file:///Users/team/Projects/Hall-NorthAccess via file

The same controls for every target

  • Quote_v3.docx
  • Acceptance_report.pdf
  • Floor_photos.zip

Trash

empty

Controls per target

3

the same for every target

In the trash

0

restorable, local only

Deleted for good

0

targets without a trash

Made-up paths and files, nothing leaves the browser. Which addresses select an access method, and that only local storage has a trash, follows the current state of k2a. The targets are examples, the list is not complete. Which actions a remote target allows is queried by k2a when it connects.

How the setup works Enter an address or pick a target. The address scheme selects the access method, the controls stay the same. Delete a file and see where there is a trash and where deleting is final.
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