Local knowledge automation

Synapse

Synapse is a local notes and RAG lab: Markdown notes are structured, made visible in a wiki, and queried through a terminal client.

  • Docker Compose
  • FastAPI
  • Qdrant
  • Ollama
  • Python
  • RAG

What the project does

Synapse connects technical Markdown notes to a local search and question-answer pipeline. Notes remain readable as simple text files, are also published to a wiki, and are indexed for semantic search. The Ask TUI lets you query your own notes and shows the source behind an answer.

Workflow

  1. 01

    Markdown note

    A learning note, lab document, or runbook kept as a simple Markdown file.

  2. 02

    Preparation

    Synapse formats and processes the note for wiki display and indexing.

  3. 03

    Wiki + index

    Wiki.js keeps the content readable while Qdrant makes it semantically searchable.

  4. 04

    Ask TUI

    The terminal client queries local knowledge and shows answers with source context.

Synapse Ask TUI answering an OSPF question from indexed notes
Local Synapse demo: a terminal question with source context.

Ask / terminal workflow

TUI demo

The GIF shows Synapse Ask in a terminal: an OSPF question is answered from indexed notes, with the answer pointing to its source. It demonstrates the core idea: local notes are not only stored, but made practically queryable.

Use Cases

Find lab knowledge quickly

Setup steps, ports, service relationships, error messages, and technical decisions can be queried from Markdown notes instead of searched manually through old files.

Technical lab knowledge stays findable without a heavy documentation system.

Make runbooks usable in the terminal

Recurring service checks, troubleshooting steps, and local setup procedures can be maintained as simple notes and queried directly in the terminal.

Repeatable admin workflows stay local, simple, and quickly accessible.

Make project documentation queryable

Synapse keeps project notes simple as Markdown while making them more useful through a wiki and semantic search.

Project knowledge remains maintainable as Markdown and becomes easier to search.

Source-backed answers instead of guessing

Answers should visibly rely on the indexed notes. Source context makes it clear where an answer came from.

The value is traceability, not free-form chat without an auditable basis.

What I learned

Synapse was mainly an exercise in making documentation practically useful. Notes only have value when they can be found, understood, and used later.

A clear flow beats buzzwords

A good RAG project becomes stronger through a traceable flow: source in, processing visible, content discoverable, answer returned with a reference.

Show the boundaries deliberately

This is a local lab system, not a production-ready knowledge platform. That keeps the focus clear: local notes, a traceable workflow, and simple terminal use.

Current state

The local note, indexing, and Ask workflow is in place and documented as a traceable flow.

The project is a local lab, not a production environment. Its features, model behaviour, and complete stack are shaped around that local use case.