- Upgrade OpenClaw primary model from deepseek-v4.1-flash to deepseek-v4.1-flash-1017 across all interactive agents, heartbeats, compaction, and cron jobs. - Configure hardened OpenRouter provider routing for 1017 (deepinfra, inference-net, parasail, cloudflare) with strict fp8/bf16 quantization and tool_choice verification. - Retain deepseek-v4.1-flash (0910), z-ai/glm-5.3-flash, and qwen3.8-flash in the automated fallback chain. - Update ADR 0002 with 1017 economics (30% price reduction on prompt/cache, +60% intelligence benchmark increase) and a 7-point provider qualification playbook. - Add operational scripts and tooling for session compaction, subagent vector deduplication, gateway preflight, and triage diagnostics in k8s/openclaw. - Update DuckDB backend engine, git-sync logic, and test suites. - Enhance Mila tracking UI components and add container build configuration. - Sync Terraform infrastructure state for Authentik.
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) format to capture intentional technical decisions, their context, considered options, trade-offs, and consequences.
📋 Record Index
| ADR | Title | Status | Date | Area |
|---|---|---|---|---|
| 0001 | Hybrid MCP Tool Search and Subagent Delegation for AI Agents | accepted |
2026-09-12 | OpenClaw / AI / MCP |
| 0002 | OpenClaw Multi-Tier Model Selection, Latency Optimization, and Inference Economics | proposed |
2026-09-13 | OpenClaw / AI / Models |
| 0003 | Everything as Code (EaC) and Reproducible Declarative Infrastructure | accepted |
2026-09-17 | Architecture / Monorepo / EaC |
| 0004 | Structured Personal Data Layer (DuckDB + JSONL in Knowledge Wiki) | accepted |
2026-10-06 | OpenClaw / Data / Storage |
| 0005 | Personal Data Isolation, Authentik Authentication Boundaries, and Hosting Segregation | accepted |
2026-10-11 | Security / Storage / Authentik |
✍️ How to Create a New ADR
- Copy the template structure into a new numbered markdown file:
docs/adr/000X-short-title-in-kebab-case.md - Include the YAML frontmatter:
--- status: "proposed | accepted | superseded | deprecated" date: YYYY-MM-DD decision-makers: ["Moritz Graf", "Antigravity"] consulted: [] informed: [] --- - 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)
- Add the new record to the table in this
README.md.