Gemma Knowledge

2026-07-02 Knowledge Management Update

Properties6
Created2026-07-02
Last updated2026-07-02
Date2026-07-02
AttendeesBijan Soltani, Jan Oboth, Justus Kneissle
Transcript—
SummaryStatus and next steps for the knowledge-management initiative - structure vs. content, and the five main workstreams.

2 min read

Knowledge Management Update

Bijan walked Jan through the current state of the knowledge-management repo, with Justus present, and we agreed on the next steps. We looked at the work through two lenses.

Perspective 1: Structure vs. content

  • Structure. Significant work remains on defining which entity types we want and their frontmatter / meta definitions (the gemma-kg type system). Bijan and Jan both work on these definitions in parallel, with Bijan as the main contributor.
  • Content. A large body of existing content still needs to be migrated into the new knowledge base.

Perspective 2: The task view - five main tasks

  1. Linear integration. Bring task management into the knowledge base.
  2. Confluence migration. Bijan starts this, beginning with Rotop and Juit as a test migration.
  3. Best-practices migration. The SQL style guide, the dbt best-practice repo, and the Airflow best-practice repo, plus authoring the entity-types process / best-practice.
  4. GemmaOS migration. Connect GemmaOS to the knowledge base. This requires a Claude skill that calls the GemmaOS API to reach its database.
  5. Access skills. Build Claude skills for reading and writing this knowledge repo.

Focus until the next meeting (Thursday, 2026-07-09)

  • Jan: tasks 1, 3, and 4.
  • Bijan: task 2 (Confluence, Rotop + Juit test), and main contributor on the frontmatter / meta definitions.
  • Both work on the frontmatter / meta (entity-type) definitions in parallel.

Graph View