Architecture Decision Records¶
Architecture decisions for the Tencent Cloud migration. Each ADR records a settled decision, its context, and its consequences.
ADRs¶
| # | Title | Status | Date |
|---|---|---|---|
| 0001 | Migration Scope and Governance | Accepted | 2026-07-24 |
| 0002 | Single Cloud Strategy — Tencent Primary | Accepted | 2026-07-24 |
| 0003 | Object Storage — Tencent COS | Accepted | 2026-07-24 |
| 0004 | Time-Series Database — TDengine | Accepted | 2026-07-24 |
| 0005 | Media Distribution — Cloudinary Fetch from COS | Accepted | 2026-07-24 |
| 0006 | Document Publishing — Cloudflare Pages + WeCom (hosting/auth superseded by 0009) | Superseded (partial) | 2026-07-24 |
| 0007 | AI Processing — Tencent CI + MetaInsight | Accepted | 2026-07-24 |
| 0008 | IoT Data Pipeline — MQTT → TDengine → COS | Accepted | 2026-07-24 |
| 0009 | Static Site Hosting — COS + EdgeOne CDN (Revised) | Accepted (Revised) | 2026-08-06 |
| 0010 | WeCom AI-Powered Internal Communications | Proposed | 2026-08-06 |
| 0011 | Universal Document URL Strategy & Publishing Pipeline | Proposed | 2026-08-06 |
| 0012 | CDN Asset Cache Optimization | Accepted | 2026-08-06 |
| 0013 | CI/CD Pipeline — GitHub Actions → COS → EdgeOne CDN | Proposed | 2026-08-07 |
| 0014 | EdgeOne CDN — COS Origin with WeCom OAuth | Accepted | 2026-08-10 |
| 0015 | Knowledge Pipeline — COS SPOT to Serve via BFFs | Proposed | 2026-08-12 |
ADR Template¶
Each ADR follows this structure:
- Title: Clear and descriptive
- Status: Proposed | Accepted | Deprecated | Superseded
- Date: YYYY-MM-DD
- Context: Why this decision is needed
- Decision: What was decided, with concrete configurations
- Consequences: Trade-offs, benefits, and risks
- Supersedes / Superseded by: Links to related ADRs when applicable
Governance (SOP)¶
All repo-persisted artifacts must map to an ADR. Reference documents, procedures, scripts, and templates — anything committed to docs/ — must trace back to a specific ADR that records the architectural decision behind it.
| Rule | Rationale |
|---|---|
| ADR first, content second | Decisions drive artifacts, not the reverse |
| ADR ←→ artifact cross-link | Every ADR links to its artifacts; every artifact links to its ADR |
ADR in docs/adr/ |
Canonical location, indexed, in mkdocs nav |
Artifacts in docs/reference/ |
Procedures, templates, scripts derived from ADR decisions |
| ADR index stays current | Must list every ADR and every derived artifact |
Example: ADR 0010 (WeCom AI) → reference/wecom-bot-creation.md (how-to guide). The ADR records the decision; the reference documents the implementation.
Numbering¶
- 0001–0099: Cloud infrastructure and platform decisions
- 0100–0199: Application and service migration decisions
- 0200–0299: Security, compliance, and operational decisions