Go to file
salah 15b11cb180 Add mermaid diagrams for infrastructure and roadmap visualizations 2026-01-28 11:23:07 +01:00
ansible adding betelgeusebytes.io deops part 2026-01-25 21:15:43 +01:00
k8s Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
.DS_Store adding betelgeusebytes.io deops part 2026-01-25 21:15:43 +01:00
ARCHITECTURE.md Remove unnecessary whitespace in architecture diagram section 2026-01-28 11:19:23 +01:00
CLAUDE.md adding betelgeusebytes.io deops part 2026-01-25 21:15:43 +01:00
DEPLOYMENT.md Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
DNS_RECORDS.txt adding betelgeusebytes.io deops part 2026-01-25 21:15:43 +01:00
FUTURE-PROJECTS.md Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
INFRASTRUCTURE.md Add mermaid diagrams for infrastructure and roadmap visualizations 2026-01-28 11:23:07 +01:00
OBSERVABILITY.md Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
README.md Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
README_old.md Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
ROADMAP.md Add mermaid diagrams for infrastructure and roadmap visualizations 2026-01-28 11:23:07 +01:00
STACK.md Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
betelgeusebytes.txt Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00
combine.sh Add observability stack and supporting scripts 2026-01-28 11:07:16 +01:00

README.md

🧠 BetelgeuseBytes AI Platform — Documentation

This documentation describes a self-hosted, CPU-first AI platform running on Kubernetes, designed to power an Islamic Hadith Scholar AI and future AI/data projects.

📚 Documentation Index

🎯 Current Focus

  • Hadith sanad & matn extraction
  • Narrator relationship modeling
  • Knowledge graph construction
  • Human-in-the-loop verification
  • Explainable, sovereign AI

🧠 What each document gives you

ARCHITECTURE

  • Logical system architecture

  • Data & control flow

  • Networking and security model

  • Design principles (CPU-first, sovereign, observable)

  • What the architecture enables long-term

This is what you show to architects and senior engineers.

INFRASTRUCTURE

  • Hetzner setup (dedicated, CPU-only, SSD)

  • Node roles and responsibilities

  • Kubernetes topology

  • Cilium networking

  • Storage layout on disk

  • Namespaces and isolation strategy

This is what you show to ops / SRE / infra people.

STACK

  • Exhaustive list of every deployed component

  • Grouped by domain:

    • Core platform

    • Databases & messaging

    • Knowledge & vectors

    • ML & AI

    • Automation & DevOps

    • Observability

    • Authentication

For each: what it does now + what it can be reused for

This is the master mental model of your platform.

DEPLOYMENT

  • How the platform is deployed (kubectl + GitOps)

  • Deployment order

  • Operational rules

  • Backup strategy

  • Day-2 operations mindset

This is your runbook starter.

ROADMAP

  • Clear technical phases:

    • Neo4j isnād schema

    • Authenticity scoring

    • Productization

    • Scaling (GPU, multi-project)

This keeps the project directionally sane.

FUTURE-PROJECTS

  • Explicitly documents that this is not just a Hadith stack

  • Lists realistic reuse cases:

    • RAG

    • Knowledge graphs

    • Sovereign AI

    • Digital humanities

    • Research platforms

This justifies the investment in infra quality.