Skip to content

companyKNOWLEDGE

companyKNOWLEDGE describes how to work with knowledge in the Open Knowledge Format (OKF): a body of knowledge does not live in a database but as a set of Markdown files in a GitHub repository or a SharePoint folder. Each file describes exactly one concept, a small block of front matter at the top of the file supplies type, tags and source, and two reserved files keep the table of contents and the change log up to date.

The practical benefit lies in the division of labour: maintaining the knowledge base — creating concepts, updating the index, recording changes — is handled by an agent in CompanyGPT, while the content itself stays where it can be versioned and reviewed. Because the bundle is at the same time connected as a collection in companyRAG, everything the agent writes is immediately searchable.

A bundle is a folder. It holds concept files plus two reserved files:

FileRole
index.mdindex pointing to the existing concepts
log.mdchange log; records what was written and when
README.mdoverview of the bundle; created with a placeholder text when the bundle is set up
Concept filesone Markdown file per concept, in subfolders of any depth

index.md and log.md are never edited by hand; they are maintained exclusively through the tools of the Knowledge connection. Subfolders are allowed and each receives its own index.

Every concept file starts with a header block (front matter), followed by free-form Markdown content:

FieldContent
titletitle of the concept
typekind of concept, for example Produktübersicht (product overview) or Architektur (architecture)
descriptionone or two sentences on what it covers
resourcethe source the concept refers to — a URL or a document from an internal system
tagskeywords for search
timestampdate of the current state

An OKF bundle is created in the knowledge area as a collection: companyRAG → Collections → Create collection, choosing OKF bundle as the collection type.

The "Create collection" dialog with the three collection types: documents, dataset and OKF bundle

The dialog describes the option as: “Point to a GitHub repository or a SharePoint folder to create a synchronised knowledge bundle.” The wizard that follows walks through details, source, location and confirmation in four steps — those steps are documented under OKF bundles.

With SharePoint as the source, the location is selected in three stages: first website or team, then the library, then the target folder via browse folders. In the final step the wizard shows a summary with name, visibility, source, site, library and path.

The option create OKF scaffold if empty is enabled there by default. In an empty location it creates the base structure so the bundle does not stay empty:

The newly created bundle folder in SharePoint containing index.md, log.md and README.md

Immediately after creation the matching collection is set up and a first synchronisation starts.