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.