feat(openclaw,infra): optimize token usage with GLM-5.3-Flash and add Garmin MCP integration
- Migrate OpenClaw primary model to z-ai/glm-5.3-flash across conductor, heartbeat, subagents, and vision - Configure deepseek-v4.1-flash and qwen3.8-flash as fallback models; retire claude-3.7-sonnet and deepseek-v4-pro - Decouple heartbeat target to prevent active session context amplification and token bleed - Add Garmin Connect MCP integration, secret unpacking, and Elite Strength Coach SOUL protocol - Add ADR 0001 documenting hybrid tool search and subagent architecture - Update Authentik configuration, theme styles, and Terraform state - Add Grafana dashboard for Taupi fan monitoring and update Velero secrets - Bump knowledge-wiki submodule pointer
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
# Architecture Decision Records (ADRs)
|
||||
|
||||
This directory documents the key architectural decisions made within the **Infrapuzzle** monorepo and its associated workloads (Kubernetes, OpenClaw AI agent, networking, DNS, and smart home systems).
|
||||
|
||||
We follow the [Markdown Architectural Decision Records (MADR)](https://adr.github.io/madr/) format to capture intentional technical decisions, their context, considered options, trade-offs, and consequences.
|
||||
|
||||
---
|
||||
|
||||
## 📋 Record Index
|
||||
|
||||
| ADR | Title | Status | Date | Area |
|
||||
| :--- | :--- | :---: | :---: | :--- |
|
||||
| [**0001**](0001-hybrid-mcp-tool-search-and-subagents.md) | **Hybrid MCP Tool Search and Subagent Delegation for AI Agents** | `accepted` | 2026-09-12 | OpenClaw / AI / MCP |
|
||||
|
||||
---
|
||||
|
||||
## ✍️ How to Create a New ADR
|
||||
|
||||
1. Copy the template structure into a new numbered markdown file:
|
||||
```bash
|
||||
docs/adr/000X-short-title-in-kebab-case.md
|
||||
```
|
||||
2. Include the YAML frontmatter:
|
||||
```yaml
|
||||
---
|
||||
status: "proposed | accepted | superseded | deprecated"
|
||||
date: YYYY-MM-DD
|
||||
decision-makers: ["Moritz Graf", "Antigravity"]
|
||||
consulted: []
|
||||
informed: []
|
||||
---
|
||||
```
|
||||
3. Clearly define:
|
||||
- **Context & Problem Statement** (Why was this decision needed?)
|
||||
- **Decision Drivers** (Constraints, costs, token limits, latency, maintainability)
|
||||
- **Considered Options** (Alternatives evaluated)
|
||||
- **Decision Outcome** (Chosen path with justification)
|
||||
- **Consequences** (Positive effects, negative trade-offs, follow-up actions)
|
||||
4. Add the new record to the table in this `README.md`.
|
||||
Reference in New Issue
Block a user