thehardwarestore.ai

EvoMap Evolver is a self-evolving AI agent engine built as a Node.js >=22.12 CLI daemon. It runs a genome-evolution loop: scans session memory/logs, extracts signals, selects 'Genes' (prompt/strategy patches) and 'Capsules' (validated skill bundles) from a local JSON/JSONL asset store, generates GEP-framed prompts for coding agents (Claude Code, Codex, Cursor, Gemini CLI, opencode, Kiro), executes those sessions, and records outcomes in a memory graph to adapt future selections. The system solidifies successful patterns into new reusable assets, auto-distills failure patterns and SKILL.md files into Genes/Capsules, and can open PRs or run validation sandboxes against candidate changes. It also ships an LLM proxy (Anthropic/OpenAI/Gemini/Vertex/Ollama routes with trace encryption and token-savings attribution), an ATP (Agent Transaction Protocol) marketplace for buying/completing agent tasks with auto-buyer and auto-deliver, a validation daemon for decentralized task verification, a local Web UI dashboard, and an experiment runner for A/B comparing evolution strategies. Hub synchronization (SSE event delivery, mailbox sync, OAuth device login) connects nodes to the evomap.ai network, but the system is designed to degrade gracefully into fully offline solo mode.

VeritasGraph is a comprehensive, governed GraphRAG and agent framework for building enterprise-grade knowledge graphs with verifiable attribution. The repository contains a core Python library (VeritasReason) for knowledge graph construction, semantic extraction, reasoning, provenance tracking, and export, along with multiple domain-specific applications: a HIPAA-safe clinical knowledge graph pipeline (clinical-kg), a floorplan extraction and validation web app (floorplan-kg), a municipality incident reporting chatbot, and a Model Context Protocol (MCP) server for IDE integration. The architecture is modular, with a plugin-based method registry pattern, unified configuration management, and a pipeline orchestration engine. While the primary character is an application framework, it also includes research-oriented components such as clinical benchmarks (MedKG-Signal) and evaluation suites, making it a hybrid project with a strong application focus.

Kotaemon is a production-grade Retrieval-Augmented Generation (RAG) application for chatting with documents. It provides a full-stack Gradio web UI with user management, document indexing (PDF, DOCX, HTML, images, web URLs), hybrid retrieval (vector + full-text), reranking, and multi-step reasoning pipelines (simple QA, question decomposition, ReWOO agent). The architecture is a monolith split into two Python libraries: `kotaemon` (core components: embeddings, LLMs, indices, storages, loaders, agents) and `ktem` (application layer: UI pages, reasoning pipelines, database models, settings). It supports multiple LLM providers (OpenAI, Azure, Anthropic, Gemini, Cohere, Ollama, LlamaCpp), embedding models, vector stores (Chroma, LanceDB, Milvus, Qdrant), and document stores. The system is highly configurable via environment variables and a settings UI. While primarily an application, it includes data/research elements such as document loaders, OCR pipelines, graph-based indexing (GraphRAG, LightRAG, NanoGraphRAG), and a training dataset for question rephrasing.

TidGi-Desktop is a cross-platform Electron application that integrates TiddlyWiki (a personal wiki) with AI agent capabilities, Git synchronization, and modern desktop features. It allows users to manage multiple workspaces (folder-based or single-file HTML wikis), sync with Git remotes, and interact with AI agents for chat, tool execution, and knowledge management. The architecture is Electron multi-process with main process, renderer processes (multiple windows), and a utility process for wiki worker. Services are wired via Inversify DI container and communicate via typed IPC (electron-ipc-cat). Key entry points include src/main.ts (Electron main), src/renderer.tsx (React renderer), src/services/agentInstance/ (AI agent lifecycle), src/services/wiki/ (wiki management), and src/services/git/ (Git operations). External dependencies include TiddlyWiki, Git (via dugite), SQLite (TypeORM), various AI SDKs (OpenAI, Anthropic, etc.), OAuth providers, and system-level integrations. The codebase is well-structured with a service-oriented architecture, extensive test coverage (unit, E2E, BDD), and a rich preference system driven by Zod schemas. It demonstrates high craftsmanship in areas like AI prompt concatenation, tool registration, and file system watching, though some modules are tightly coupled to the application's domain.

LeanKG is a Go-based knowledge graph engine for AI-assisted development. It indexes source code from multi-language repositories into a graph of elements (functions, types, classes) and relationships (calls, imports, implements), stored in SQLite or PostgreSQL with optional vector embeddings for semantic search. The system provides a CLI, REST API, MCP (Model Context Protocol) server, and a React web UI (force-directed graph, file tree, code panel). Core capabilities include incremental indexing with three-signal change detection, a four-tier query ladder (cold/exact/fuzzy/semantic), impact analysis with blast radius, organizational knowledge management (incidents, notes, env reports), ontology matching, federation across servers, and token-budgeted compression for AI tool integration. The architecture is modular: the store backend interface supports SQLite and PostgreSQL with a shared migration ledger; indexing uses regex extractors for 40+ languages with an optional tree-sitter CGO tier; embeddings use a provider abstraction (OpenAI-compatible, llama.cpp sidecar, deterministic). The codebase is well-structured with extensive tests, hermetic test patterns, and deterministic output design. Notable reusability includes the compress package (shell output, git diff), auth token system, store abstraction pattern, and A/B benchmarking harness.

Supermemory is a commercial-grade AI memory and context engine that provides persistent long-term memory for AI agents. The repository implements the client-side integration SDKs, an MCP (Model Context Protocol) server, a memory graph visualization component, and supporting infrastructure. In production, it connects to an external cloud API (api.supermemory.ai) that handles document ingestion, semantic search, user profiles, and knowledge graph construction. The codebase is organized as a monorepo with distinct packages for TypeScript/Python SDKs covering multiple AI frameworks (Vercel AI SDK, OpenAI, Mastra, Claude, etc.), a Cloudflare Workers-based MCP server with OAuth and widget UI, a ship-grade memory-graph React component with force-directed canvas rendering, and a comprehensive validation schema package. The architecture demonstrates strong engineering practices: strict Zod validation, middleware injection patterns, caching and deduplication logic, and thorough testing across languages. Notable skill is evident in the memory-graph canvas engine (viewport, simulation, spatial indexing, version chain visualization) and the shared memory-context injection utilities. The main downside is significant logic duplication across four Python SDK packages and their TypeScript counterparts, which increases maintenance risk. The repo is actively developed with CI/CD pipelines publishing to npm and PyPI.

This repository is a full-stack application for building knowledge graphs from unstructured data using Large Language Models (LLMs). The backend, built with FastAPI and LangChain, ingests documents from multiple sources (local files, web pages, YouTube, Wikipedia, S3, GCS), chunks them, and uses an LLM to extract entities and relationships, which are stored in a Neo4j graph database. The frontend, a React/TypeScript application, provides a user interface for uploading files, configuring extraction (schema, LLM model, chunking), visualizing the resulting graph, and interacting with the data through a retrieval-augmented generation (RAG) chatbot with multiple retrieval modes (vector, graph, fulltext, hybrid). The system includes post-processing features like community detection, deduplication, and orphan node cleanup, as well as token usage tracking and evaluation metrics (RAGAS). While primarily an application with a web UI, it also contains experimental notebooks (GraphRAG, chunk size evaluation) that serve a data research purpose, making it a hybrid codebase with a dominant application character.

LeanRAG is a Retrieval-Augmented Generation (RAG) framework that leverages knowledge graph structures with semantic aggregation and hierarchical retrieval to generate context-aware, concise, and high-fidelity responses. The system processes documents through a pipeline: chunking, LLM-based triple extraction, hierarchical graph construction with clustering, and structure-guided retrieval from fine-grained entities upward through the graph to reduce redundancy and improve evidence quality. It targets question-answering tasks across domains (general, CS, legal, agriculture) and uses LLMs (OpenAI, Qwen, DeepSeek) for extraction and generation, with Milvus for vector search and MySQL for storing graph entities, relations, and communities. Evaluation is performed via an external LLM API scoring answers on comprehensiveness, empowerment, diversity, and overall quality.

Hyper-RAG is a hypergraph-driven Retrieval-Augmented Generation (RAG) system designed to reduce LLM hallucinations by modeling beyond-pairwise correlations in domain knowledge. The repository provides both a Python library (`hyperrag`) and a full-stack web application with a FastAPI backend and React frontend. The core innovation is the use of hypergraphs to represent complex relationships among entities, outperforming traditional graph-based RAG methods like Graph RAG and Light RAG. The system supports multiple query modes: hyper (full hypergraph), hyper-lite, graph, naive, and direct LLM, with streaming responses. Architecture: The Python library (`hyperrag/`) implements the RAG pipeline: text chunking, entity extraction via LLM, hypergraph construction, vector embedding storage (NanoVectorDB), and query execution. The web UI (`web-ui/`) consists of a FastAPI backend (`main.py`) exposing REST endpoints for file upload, database CRUD, and HyperRAG queries, plus a React frontend with Ant Design and Graphin for interactive chat, hypergraph visualization, and settings management. Docker Compose orchestrates the frontend, backend, and Nginx reverse proxy. Key entry points: `hyperrag/hyperrag.py` (HyperRAG class), `service_api.py` (standalone API), `web-ui/backend/main.py` (FastAPI app). External dependencies include OpenAI/Azure/Bedrock LLM APIs, NanoVectorDB, tenacity, aiofiles, and various Python packages. The system is configurable via `config_temp.py` and `settings.json`. Data flows: Raw text (uploaded or provided) is chunked, entities and relationships are extracted via LLM, hyperedges are constructed, and embeddings are stored. Queries are processed by selecting relevant hyperedges and entities, constructing a context, and generating a response. The system caches LLM responses and supports real-time logging via WebSocket during embedding.

Sparnatural is a client-side, web-component-based visual SPARQL query builder. It allows non-technical users to construct complex SPARQL SELECT queries by selecting classes, properties, and values through an interactive criteria tree, with support for AND/OR, OPTIONAL, NOT EXISTS, aggregated variables, and geospatial filters. The system is configurable via SHACL or OWL shape definitions, which define available entities, properties, widgets, and datasources. It integrates with YASGUI for query editing and result display, and provides multiple built-in widget types (list, autocomplete, tree, map, date range, number, boolean, search). The core architecture is a custom HTML element (`<spar-natural>`) with a component-based UI, event-driven state management (ActionStore), and a SPARQL generation pipeline that converts an internal JSON query format to SPARQL algebra using sparqljs. The codebase demonstrates solid engineering with clean interfaces for specification providers and data providers, but carries technical debt from a legacy OWL configuration path, two query JSON formats (v1 and v13), heavy jQuery/DOM manipulation, and limited test coverage outside the SPARQL translator. It is actively maintained and well-documented, but its tight coupling to SPARQL endpoints and large dependency bundle may limit reuse in non-RDF contexts.

This repository implements a full-stack AI-powered food recommendation application called '今天吃什么' (What to eat today). The system combines a Next.js frontend with a Python Flask backend that uses a GraphRAG (Retrieval-Augmented Generation) architecture leveraging Neo4j for graph-based recipe relationships and Milvus for vector similarity search. Users interact via a chat interface to receive personalized recipe recommendations with step-by-step cooking instructions. The application includes a comprehensive recipe knowledge base in markdown format, Docker-based deployment orchestration, and a modular RAG pipeline with intelligent query routing and session management.

This repository is a starter template for creating documentation websites using the Hugo Blox framework. It provides a pre-configured Hugo site with example content, navigation, and configuration files for a documentation theme. The actual functionality (rendering, shortcodes, search) is delegated to imported Hugo modules from the HugoBlox/kit ecosystem. The repo contains no application logic or data pipelines; it is purely a content and configuration scaffold intended to be cloned and customized. The architecture is a static site generator with Tailwind CSS, Pagefind search, and GitHub Actions CI/CD. Key entry points are the hugo.yaml, params.yaml, and menus.yaml configuration files, and the content/Markdown files. External dependencies include Hugo, the HugoBlox modules, Node.js (for Tailwind and Pagefind), and a hosting provider.