Phoenix × 6D Foraging
Diagnose the cascade before you light the fire.
How 6D Informs Phoenix
The 6D Foraging Methodology analyzes systems across six dimensions: Customer (D1), Employee (D2), Revenue (D3), Competitive (D4), Quality (D5), and Operational (D6). When applied to a legacy system, it reveals:
- Which dimensions are degrading — is the legacy system causing operational failures (D6), quality issues (D5), or competitive disadvantage (D4)?
- Where the cascade originates — is the technical debt the cause or the symptom?
- How severe the impact is — measured through the Fetch score
The Diagnostic Phase
Before a Phoenix engagement begins, a 6D diagnostic answers the fundamental question: should this system be Phoenixed at all?
Not every legacy system needs transformation. Some are stable, well-understood, and cost-effective to maintain. The 6D diagnostic distinguishes between:
| 6D Finding | Recommendation |
|---|---|
| Single-dimension issue (e.g., D5 quality) | Targeted fix, not Phoenix |
| Multi-dimension cascade with operational origin (D6) | Strong Phoenix candidate |
| Revenue impact (D3) driven by competitive gap (D4) | Phoenix if legacy is the bottleneck |
| Employee dimension (D2) degrading due to system | Phoenix — talent retention at risk |
Cascade Analysis as Input
The 6D cascade analysis becomes a strategic input for the Phoenix pipeline:
- Agent 1 (Extractor) focuses extraction effort on the dimensions identified as cascade origins
- Agent 3 (Synthesizer) prioritizes requirements that address the diagnosed cascade
- Agent 4 (Architect) designs the new system to resolve the specific dimensional weaknesses
- Agent 6 (Validator) tests not just functional equivalence but dimensional improvement
Example: UC-024
UC-024: The Obsolescence Cascade analyzed software engineering's existential transition across five dimensions. The 6D diagnostic revealed:
- Origin: D2 (Employee) + D6 (Operational) — a dual-origin cascade
- Cascade: Hiring collapse (D2) → quality erosion (D5) → competitive disadvantage (D4) → revenue pressure (D3)
- Implication: Organizations maintaining legacy systems face compounding risk as the talent pool to maintain those systems shrinks
This is exactly the scenario where Phoenix becomes essential — not because the system is broken, but because the ability to maintain it is evaporating.
"6D tells you where the fire is spreading. Phoenix tells you what to rebuild from the ashes."