Atomic looks quite interesting, and the "wiki synthesis" is particularly interesting:
I've been working on a suite of skills and a tiny MCP (also SQLite + SQLite-vec based) where the focus is on making it easy to produce "atoms" from quick brain dumps.
The chunking problem is "bypassed" by declaring each section a chunk, and having the LLMs rewrite drafts to sections that chunk well. That means lots of redundancy, and no "As explained above".
The intended reader isn't a human, but rather agents that generate human-friendlier prose, for different target audiences. By assuming the reader is an "expert", the idea is that it's much cheaper to mass-produce reviewed "atoms".
Itching to try that workflow with Atomic or Tolaria.
Cognite | Oslo, Norway and Austin, US | Full time | On-site (we help relocate) or remote | https://www.cognite.com/en/careers
Cognite provides contextualised data as a service, such as digital twins, focusing on asset heavy industries to start with.
We're hiring for several positions. Most are on-site, but we're looking for a principal database reliability engineer (DBRE) with Kafka and Kubernetes chops, and a senior/principal DBRE with Elasticsearch, Kafka, or FoundationDB experience.
The DBRE positions are offered remote in EU + US time zones, the rest are mostly in on-site Oslo, Norway. We help with relocation.
https://www.cognite.com/en/careers
I've been working on a suite of skills and a tiny MCP (also SQLite + SQLite-vec based) where the focus is on making it easy to produce "atoms" from quick brain dumps.
The chunking problem is "bypassed" by declaring each section a chunk, and having the LLMs rewrite drafts to sections that chunk well. That means lots of redundancy, and no "As explained above".
The intended reader isn't a human, but rather agents that generate human-friendlier prose, for different target audiences. By assuming the reader is an "expert", the idea is that it's much cheaper to mass-produce reviewed "atoms".
Itching to try that workflow with Atomic or Tolaria.