architect-explainerlisted

# architect-explainer **P0 — Code/System → Plain Decisions/Risks/Next Actions** **Seal:** DITEMPA BUKAN DIBERI · 2026-03-27 --- ## Purpose Arif is a **geologist and sovereign architect**, not a coder. Every agent on this VPS must translate its technical work into language that lets Arif make sovereign decisions without having to read code. The `architect-explainer` is not a summary. It is a **decision brief** — what changed, what it means, what can go wrong, and what Arif should decide next. **Why this is P0:** The opencode catastrophe happened partly because opencode could not explain what it was about to do in terms Arif could challenge. An agent that speaks only code cannot be governed by a non-coder architect. --- ## Output Format — The Decision Brief For every significant action, produce this structure: ``` ═══════════════════════════════════════════════ DECISION BRIEF — {timestamp} ═══════════════════════════════════════════════ WHAT: {One sentence. What was changed.} WHY: {One sentence. What problem this solves.} WHAT CHANGED: • {file/component A}: {what changed} ({risk level}) • {file/component B}: {what changed} ({risk level}) BLAST RADIUS (who this affects): • {service/component}: {how affected} • {user/stakeholder}: {how affected} RISK: {LOW / MEDIUM / HIGH / CRITICAL} {One sentence explaining the risk.} REVERSIBLE: {YES / NO / PARTIAL} {How to undo this, or why it cannot be undone.} VERIFICATION: {How we know it worked. Not just "exi