Phoenix × Fetch

The action layer determines when to ignite.

How Fetch Triggers Phoenix

The Fetch Framework is the action layer of the Cormorant stack. It calculates a score — Fetch = Chirp × |DRIFT| × Confidence — that determines whether the gap is large enough to warrant action.

For legacy modernization, Fetch scoring answers: how urgently does this system need Phoenix?

---

Fetch Decision Thresholds

Fetch Score	Action	Legacy Context
High (Execute)	Act immediately	Critical system — Phoenix engagement now
Medium (Confirm)	Validate and act	Important system — schedule Phoenix, begin diagnostic
Low (Queue)	Monitor	Stable system — continue maintenance, reassess quarterly
Minimal (Wait)	No action	Healthy system — no modernization needed

---

Scoring Legacy Systems

When evaluating a portfolio of legacy systems for Phoenix prioritization, Fetch's three components map naturally:

Chirp (Signal Strength)

How loud is the signal that this system needs modernization?

• Incident frequency increasing?
• Maintenance costs rising?
• Users complaining?
• Regulatory pressure building?

DRIFT (Gap Size)

How far is the current system from where it needs to be?

• How outdated is the technology stack?
• How large is the functional gap vs. modern alternatives?
• How much technical debt has accumulated?

Confidence

How certain are we that modernization will improve the situation?

• Is the business logic well-understood?
• Are stakeholders available for tribal knowledge transfer?
• Is the target architecture proven?

---

Portfolio Prioritization

Organizations with multiple legacy systems use Fetch scoring to prioritize the Phoenix pipeline:

System A:  Fetch = 0.92  →  Execute  →  Phoenix Phase 1
System B:  Fetch = 0.71  →  Confirm  →  Phoenix Phase 2
System C:  Fetch = 0.45  →  Queue    →  Monitor, reassess
System D:  Fetch = 0.18  →  Wait     →  Continue maintenance

This prevents the common mistake of Phoenixing everything at once. Start with the highest-urgency system, learn from the engagement, and apply those lessons to the next.

---

Feedback to Fetch

After a Phoenix engagement completes, the Fetch score for the transformed system should drop significantly — the gap has been closed. This feeds back into the Cormorant stack as confirmation that the action was correct.

If the Fetch score remains high after transformation, it indicates the Phoenix pipeline missed something — a signal for the GESA learning layer to capture.

---

"Fetch measures the urgency. Phoenix delivers the transformation."