Architecture Decisions¶

Key design decisions and their rationale.

Decision Framework¶

graph LR
    PROBLEM["Problem:<br/>Monolithic Skills<br/>+ High Token Cost<br/>+ Context Degradation"]

    DECISION1["Decision 1<br/>Model Routing<br/>Opus/Sonnet/Haiku"]
    DECISION2["Decision 2<br/>Scope Decomposition<br/>Split Skills → Sub-agents"]
    DECISION3["Decision 3<br/>Endpoint Grouping<br/>Threshold: 12 endpoints"]
    DECISION4["Decision 4<br/>Wave Scheduling<br/>12 Waves of 3 agents"]
    DECISION5["Decision 5<br/>Token Budget<br/>2-2.5x cost, 6-8 scans/week"]

    PROBLEM --> DECISION1
    DECISION1 --> DECISION2
    DECISION2 --> DECISION3
    DECISION3 --> DECISION4
    DECISION4 --> DECISION5

    style PROBLEM fill:#9b30ff,color:#fff,stroke:#00e5ff,stroke-width:2px
    style DECISION1 fill:#4a148c,color:#fff
    style DECISION2 fill:#6a1b9a,color:#fff
    style DECISION3 fill:#7b1fa2,color:#fff
    style DECISION4 fill:#8e24aa,color:#fff
    style DECISION5 fill:#9c27b0,color:#fff

Key Decisions¶

• Model Routing Rationale — Why V3 Pragmatica
• Scope Decomposition — Why split monolithic skills
• Endpoint Split Strategy — Why threshold 12, cap at 3
• Wave Schedule Design — Why 12 waves, ordering logic
• Token Budget Analysis — Cost projections, ROI