3e7eddc074
This commit implements comprehensive production hardening across multiple layers to prepare StemeDB for enterprise pilot deployments: ## API Layer - Add rate limiting middleware with configurable limits per endpoint - Enhance error handling with detailed context and proper HTTP status codes - Add security hardening tests for input validation and boundary conditions - Create store_helpers module for defensive storage access patterns ## Storage & WAL - Optimize group commit batching for higher throughput - Add defensive error handling in hybrid backend with proper fallbacks - Enhance WAL journal durability guarantees with fsync validation - Improve index store query performance with better caching ## Operations & Deployment - Add comprehensive operations documentation (deployment, monitoring, DR) - Create systemd units for backup, WAL archival, and verification - Add monitoring configs (Prometheus alerts, metrics exporters) - Implement backup/restore scripts with verification and S3 archival - Add DR drill automation and runbook procedures - Create load balancer configs (nginx, envoy) with health checks ## Documentation - Update CLAUDE.md with operations and troubleshooting guides - Expand roadmap with production readiness milestones - Add pilot success criteria and deployment reference architecture - Document TLS setup, monitoring integration, and incident response ## Configuration - Add .env.example with all required environment variables - Document resource sizing for different deployment scales - Add configuration examples for various deployment topologies This positions StemeDB for successful enterprise pilots with proper operational discipline, monitoring, backup/DR, and security hardening. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| about | ||
| app-concepts | ||
| archive | ||
| demo/vulnbank | ||
| guides | ||
| legal | ||
| operations | ||
| presentations | ||
| references/go-adk | ||
| research | ||
| rfcs | ||
| sdk | ||
| specs | ||
| consistency-model.md | ||
| data-structures.md | ||
| README.md | ||
Episteme Documentation
Complete documentation for Episteme (StemeDB) - a probabilistic knowledge graph database.
Getting Started
First Steps
- Quick Start - Get running in 5 minutes
- What is Episteme? - Core concepts and examples
- Architecture Overview - Technical design
- Vision - Product philosophy
Use Cases
- Use Cases Index - All scenarios
- Consumer Health Intelligence - Drug safety tracking
- Financial Due Diligence - M&A analysis
- Agile Agent Team - AI collaboration
- GLP-1 Living Review - Real-world example
Application Development
Building on Episteme
- App Concepts Index - Application layer patterns
- Consumer Health Vertical - Healthcare application design
- Boundary Principles - What Episteme does vs. what your app does
SDKs & Integration
- Go SDK Guide - HTTP client with Ed25519 signing
- Go Usage Examples - Fluent builders and patterns
- ADK-Go Reference - AI agent integration
- ADK-Go Examples - Agent patterns (chatbot, researcher, etc.)
Technical References
Core Architecture
- Data Structures - Assertion, Vote, Epoch, MaterializedView
- Consistency Model - Conflict resolution and convergence
- Governance Models - Authority hierarchies
Advanced Topics
- Distributed Write Path - Clustering and sharding
- WAL Crash Recovery - Storage durability
- Concept Hierarchy - Subject/predicate organization
- Visual Hash Query - Screenshot-based retrieval
Specifications
- RFCs Index - All RFCs
- RFC-001: Enterprise Policy Aliases - Multi-tenant policy
Development Guides
Setting Up
- Local Development Setup - Environment configuration
- Testing Guide - Running test suites
- Quality Checks - Pre-commit hooks
- Coding Guidelines - Rust standards
How-To Guides
- Adding a Domain - Extend ontology for new verticals
- Implementation Audit Checklist - Production readiness
- Writing UAT Reports - User acceptance testing
Integration Guides
- AI Coding Assistant Integration - Claude/Cursor setup
- ADK-Go + Episteme - Building agents
Demos & Examples
- VulnBank Demo - Security vulnerability tracking example
Project Planning
Current Work
- Roadmap - Current and planned features
- Roadmap Archive - Completed phases
Specifications & Planning
- Aphoria Claims API - Claims management design
- Ontology Layer: Medical Vertical - Healthcare domain modeling
About Episteme
Vision & Strategy
- Market Position - Competitive landscape and thesis
- Simulation Vision - Agent-based validation
Legal
- Patent Disclosure - IP documentation
- Patent Figures - Visual diagrams
- Patent Specification - Technical claims
Tools & Infrastructure
- Grafana Dashboard - Metrics visualization
- Presentations - Slide decks and demos
Archive
Historical documentation and snapshots:
- Documentation Updates Summary - 2026-02-08 audit
- Corpus Quick Start - Legacy setup guide
Quick Reference: What Goes Where
| If you need to... | Episteme provides... | You build... |
|---|---|---|
| Store conflicting facts | Assertion type, append-only DAG | Nothing - just POST assertions |
| Resolve conflicts | Lenses (Recency, Consensus, Skeptic) | Lens selection logic |
| Query historical state | as_of parameter |
Time-travel UI |
| Track changes | since parameter + MV changelog |
Notification system |
| Weight by source authority | source_class field + decay |
Tier classifier |
| Detect emerging signals | Skeptic Lens + conflict_score | Gardener (threshold logic) |
| Show per-tier consensus | Layered Consensus Lens | Dashboard UI |
| Extract claims from papers | Nothing - pre-assertion transform | NLP pipeline |
| Sign assertions | Signature verification | Agent wallet / key management |
| Generate summaries | Structured query responses | LLM summarizer |
Contributing
See CONTRIBUTING.md for:
- Documentation standards
- File organization principles
- How to add new guides
- Review process
Navigation Tips
- Breadth-first: Start with What is Episteme? → Use Cases → Quick Start
- Depth-first: Start with Architecture → Data Structures → Distributed Write Path
- Hands-on: Start with Quick Start → Go SDK → App Concepts