A newer version of the Gradio SDK is available:
6.1.0
DeepBoner Documentation
Welcome to the DeepBoner documentation. This directory contains comprehensive documentation for developers, contributors, and operators.
Quick Navigation
| Need to... | Go to... |
|---|---|
| Get started quickly | Getting Started |
| Understand the architecture | Architecture Overview |
| Assess production readiness | Production Readiness |
| Set up for development | Development Guide |
| Deploy the application | Deployment Guide |
| Look up configuration | Reference |
| Track technical debt | Technical Debt |
Documentation Structure
docs/
βββ README.md # This file - documentation index
β
βββ getting-started/ # Onboarding documentation
β βββ installation.md # Installation guide
β βββ quickstart.md # 5-minute quickstart
β βββ configuration.md # Configuration guide
β βββ troubleshooting.md # Common issues and solutions
β
βββ architecture/ # System design documentation
β βββ overview.md # High-level architecture
β βββ agent-tool-state-contracts.md # Agent/Tool/State contracts (CRITICAL)
β βββ production-readiness.md # Enterprise gap analysis (HONEST)
β βββ system-registry.md # Service registry (canonical wiring)
β βββ workflow-diagrams.md # Visual workflow diagrams
β βββ component-inventory.md # Complete component catalog
β βββ data-models.md # Pydantic model documentation
β βββ exception-hierarchy.md # Exception types and handling
β
βββ development/ # Developer guides
β βββ testing.md # Testing strategy and patterns
β βββ code-style.md # Code style and conventions
β βββ release-process.md # Release workflow
β
βββ deployment/ # Deployment documentation
β βββ docker.md # Docker deployment
β βββ huggingface-spaces.md # HuggingFace Spaces deployment
β βββ mcp-integration.md # MCP server setup
β
βββ technical-debt/ # Known issues and improvements
β βββ index.md # Technical debt overview
β βββ debt-registry.md # Itemized debt tracking
β
βββ reference/ # API and configuration reference
β βββ configuration.md # All configuration options
β βββ environment-variables.md # Environment variable reference
β
βββ bugs/ # Bug tracking (existing)
β βββ active-bugs.md
β βββ p3-progress-bar-positioning.md
β
βββ decisions/ # Architecture Decision Records (existing)
β βββ 2025-11-27-pr55-evaluation.md
β
βββ future-roadmap/ # Future feature specs (existing)
βββ 16-pubmed-fulltext.md
Documentation Standards
File Naming
- Use kebab-case for all filenames (e.g.,
getting-started.md) - Keep names descriptive but concise
Content Guidelines
- Start each document with a clear title and purpose
- Include a table of contents for longer documents
- Use Mermaid diagrams for visual documentation
- Link to related documentation
- Keep content current - update when code changes
Markdown Conventions
- Use ATX-style headers (
#,##, etc.) - Code blocks with language specification
- Tables for structured data
- Admonitions for warnings/notes (where supported)
Key Documents
For New Developers
- Installation - Set up your environment
- Quickstart - Run your first query
- Architecture Overview - Understand the system
- Testing - Run and write tests
For Contributors
- CONTRIBUTING.md - Contribution guidelines
- Code Style - Style conventions
- Testing - Testing requirements
For Operators
- Docker Deployment - Container deployment
- HuggingFace Spaces - Cloud deployment
- Configuration Reference - All options
For Understanding the Codebase
- Agent-Tool-State Contracts - CRITICAL - Agent coordination contracts
- Component Inventory - All modules
- Data Models - Core types
- System Registry - Service wiring
- Technical Debt - Known issues
Related Documentation
- README.md - Project overview and quick start
- CLAUDE.md - AI agent developer reference
- CHANGELOG.md - Release history
- SECURITY.md - Security policy
- CODE_OF_CONDUCT.md - Community guidelines
Contributing to Documentation
Documentation is code. Please:
- Keep docs updated when changing related code
- Follow the naming and style conventions
- Test links before committing
- Add new documents to this index
See CONTRIBUTING.md for full guidelines.
"Well-documented boners only. We take evidence-based documentation very seriously." π