Engagement Path Classifier

# Engagement Path Classifier

## Purpose

Classify a likely engagement path from distilled client context. The
classification should help the team choose the smallest useful set of
playbooks, questions, and artifacts.

Do not force one path when the evidence points to a hybrid engagement.
Preserve uncertainty and explain the rationale.

## Inputs

Use one or more of:

- Engagement context summary.
- Kickoff notes or transcript.
- Statement of work or sales brief.
- Current-state summary.
- Known business outcomes, deadlines, and constraints.

## Supported paths

Consider these paths:

- Brownfield platform or DevOps assessment.
- Greenfield platform build.
- Kubernetes rescue or stabilization.
- Compliance or security acceleration.
- Cost optimization sprint.
- Greenfield software product build.
- Legacy software modernization.
- Internal tooling or workflow automation.
- Data, API, or third-party integration project.
- Hybrid engagement that combines several paths.

## Process

1. Identify the primary business outcome.
2. Identify the system type: platform, application, data, operations,
   security, compliance, cost, or delivery workflow.
3. Identify urgency: exploratory, planned delivery, rescue, deadline
   driven, or risk driven.
4. Match evidence to one or more paths.
5. List the bluebook pages that should guide the next discovery step.
6. Assign confidence and explain what would change the classification.

## Output format

```markdown
# Engagement Path Recommendation

## Recommended path

Primary path:
Confidence: High / Medium / Low

Why this path fits:

- Evidence:
- Reasoning:

## Secondary or hybrid paths

| Path | Why it may apply | Evidence | Confidence |
| ---- | ---------------- | -------- | ---------- |
|      |                  |          |            |

## Bluebook pages to use next

| Page | Why it matters now |
| ---- | ------------------ |
|      |                    |

## What would change this recommendation

- [ ] Missing evidence:
- [ ] Stakeholder question:
- [ ] Technical question:

## Recommended next step

Run the Discovery Gap Finder against this path before creating a
roadmap or backlog.
```

## Quality bar

- Cite evidence for the selected path.
- Prefer a hybrid path over a false single answer.
- Do not recommend tools before evidence supports the problem shape.
- Include software delivery paths, not only platform paths.
- Mark low-confidence classifications clearly.