SUM EQUITIES

Orbitio — Self-Organizing Knowledge Engine

A knowledge system that organizes notes into a navigable, queryable space — auto-tagged, summarized, and traversable through a visual knowledge garden.

In development Verified Jun 6, 2026

Coming soon
Orbitio — Knowledge graph visualization

Status: in development, no public artifact yet. The source repo is private and there is no live demo a visitor can interact with. The description below reflects the local-bring-up state of the system, not an externally-verifiable shipping product.

“ORBITIO — where every idea finds its orbit.”

A self-organizing knowledge engine. Feed it notes; it organizes them into a navigable, queryable space, auto-tags and summarizes content, and surfaces relationships through a visual knowledge garden.

What teams can do with Orbitio

  • Stop losing what they already know. Notes, captures, and references become a connected graph instead of a folder of orphaned files.
  • Discover unexpected links. Similarity alerts surface connections between new content and prior thinking that flat search would miss.
  • Capture in one motion. A browser extension lets web content land directly in the knowledge base without copy-paste rituals.
  • Stay in sync across surfaces. A local watcher keeps an existing notes folder mirrored into the engine without changing the writing workflow.

Typical use cases

  1. Researchers and analysts building a personal knowledge graph that grows with reading.
  2. Consulting teams maintaining cross-engagement institutional memory that survives turnover.
  3. Founders and operators keeping market, product, and competitive notes navigable across many domains.

Status

The core ingest → embed → search path runs end-to-end and is covered by a passing test suite (15 tests, no external infrastructure) and a committed retrieval eval (flat keyword baseline recall@1 = 0.83, recall@3 = 1.0 on an 18-question golden set); vector and Ragas metrics await a keyed eval run. The local Lefthook gate passes; hosted GitHub Actions is currently billing-paused (its checks show red because jobs can’t start, not from test failures). The repo is private with no public artifact, so none of this is externally interactive. Source and architectural detail are not currently published; case study and technical deep-dive available on request for serious inquirers via the contact page.

What’s Needed For This Entry To Tighten

  • A public demo URL exposing the knowledge garden view, and/or
  • A public source repository linked via githubUrl.

Related work