Skip to content

engineering-os

A personal OS for cloud and infrastructure engineers: your notes as a queryable knowledge base, wired into AI coding agents. Everything runs locally.

What you get from one clone

  • An Obsidian vault template scaffolded for the five domains an infra engineer actually works in: CloudOps, FinOps, DevOps, SecOps, Architecture.
  • A local hybrid RAG index over your vaults: a small TypeScript service over SQLite + sqlite-vec + FTS5, vector search fused with BM25, optional MMR reranking. No Python, no PyTorch, no cloud. Your notes never leave your machine.
  • An HTTP search server your AI agent (Claude Code or any MCP-capable client) can query for grounded context.
  • Three vaults with a write-routing contract, a standards governance layer, and ADR scaffolding.

Where to go next

  • Quickstart - clone, build, index, search in about 15 minutes.
  • Concepts - the three vaults, unified reading vs segregated writing, and the hybrid retrieval pipeline.
  • The five domains - how the work vault is organized.
  • RAG layer - the eos-rag service, its search API, and model choice.
  • Working layer - beads for agent tasks, the vault for narrative.
  • Work-graph dashboard - the beads graph by project, with the ready queue.
  • Standards - the governance layer and how it is distributed.
  • Architecture - the decisions behind the design.

Status

v0.1. The vault template, the TypeScript RAG layer, the standards layer with the plan and clone-projects skills, work-tracking (beads Phase A), the work-graph dashboard, and this docs site are all in place. Claude Code hooks and the Linear/planning phases of the working layer come next.