Skip to main content

Architecture Decision Records (ADR) Reference

πŸ“ Location​

All SPECTRE architectural decisions are documented in the centralized ADR Ledger:

Repository: adr-ledger Document: docs/SPECTRE_ARCHITECTURE_DECISIONS.md

🎯 Formal ADRs​

πŸ“‹ Documented Decisions​

The consolidated document includes 11 architectural decisions:

Critical (4)​

  1. Nix-First Kubernetes Orchestration over Helm
  2. Argon2id KDF for Secret Encryption (security fix)
  3. Ingress + cert-manager Architecture
  4. NATS JetStream Event-Driven Architecture

Major (4)​

  1. Token Bucket Rate Limiting Strategy
  2. Three-Tier RBAC Hierarchy (admin > service > readonly)
  3. Prometheus + OTLP Observability Stack
  4. Graceful Shutdown with SIGTERM/SIGINT Handling

Implementation (3)​

  1. Shared HTTP Client with Connection Pooling
  2. Health Check Endpoints (/health, /ready, /metrics)
  3. Structured JSON Error Responses

πŸ“– Why Centralized?​

Architectural decisions are maintained in the central adr-ledger repository for:

  • Cross-Project Visibility: Decisions can be referenced by other projects (CEREBRO, PHANTOM, NEUTRON)
  • Governance: Formal review and approval process
  • Traceability: Complete audit trail of all architectural choices
  • Knowledge Management: Centralized intelligence for the entire ecosystem

πŸš€ How to Propose New ADRs​

For new SPECTRE architectural decisions:

  1. Use the ADR MCP tools: adr_new, adr_accept
  2. Or manually create in adr-ledger/adr/proposed/
  3. Follow the ADR template structure
  4. Submit for review and acceptance

For implementation details and code, see SPECTRE's inline documentation and KUBERNETES.md.