coding-compare-architectures

name	coding-compare-architectures
description	Compare an existing architecture/solution against a specific reference and decide KEEP, PARTIAL ADOPT, or REPLACE with explicit migration steps. Use only when both current-state material and a concrete reference are provided.
metadata	{"short-description":"Compare current architecture with a reference"}

Compare Architectures

Purpose: compare the current architecture or solution with a concrete reference and decide whether to keep it, partially adopt the reference, or replace it.

Input

• Mine: code / doc / architecture (partial ok)
• Reference: file(s) or link(s)
• Goal: what we optimize for (perf, cost, simplicity, scale, reliability)

If inputs are incomplete, ask only blocking questions (max 3).

Method

1. Normalize both designs into the same model:

   • components
   • data flow
   • state/storage
   • failure modes
   • performance characteristics
   • operational complexity
   • testability

2. Diff:

   • identical
   • materially different
   • hidden assumptions

3. Decide:

   • KEEP / PARTIAL ADOPT / REPLACE
   • justify with concrete tradeoffs (not vibes)

4. If decision ≠ KEEP, produce a spec:

   • Spec v1 (bullets)
   • What changes (explicit)
   • What stays (explicit)
   • Migration steps (ordered)
   • Compatibility risks
   • Verification plan

Policy

• AVOID backward compatibility by default; include compatibility work only when explicitly requested.

Output

Diff

• ...

Tradeoffs

• ...

Decision

• KEEP | PARTIAL ADOPT | REPLACE
• Why:

Spec (only if change)

• Spec v1:
• Migration:
• Verification: