Target-state design

Phase 3 is a four-step stepper. A persistent sidebar tracks the phase gate, coverage metrics, and the recommendation summary; a bottom bar shows readiness progress and the Lock & Advance button.

1 · Design brief

A design statement — the framing for the target state, generated from Phase 1 and Phase 2 and edited by the team. Everything downstream reads it.

2 · Gap resolution

For every gap, you build a closure chain — the traced line from the problem to the thing that resolves it:

gap → recommendation → target process → data objects → application → capability

• The recommendation engine proposes recommendations, grounded on the standards library and the current model, with a hallucination filter.
• You confirm each slot of the chain. A critical gap can’t be marked resolved until its chain is complete — that’s the gate that defines the product.
• Recommendations you don’t want can be deferred (and can resurface in a follow-on engagement).

3 · Target architecture

The dual canvas — current architecture and proposed architecture, side by side, so every proposed change is anchored to something real. Tabs are driven by the gap dimensions in play.

• eavantage can draft a target process (a TO-BE BPMN flow) for the team to refine. The draft is never published automatically — it stays a draft until a person approves it.
• Candidate recommendations are checked against the model and the standards library before they’re shown.

4 · Client commitment

The implementation plan — each committed change recorded against the client’s sign-off, so at closure there’s a clear line from “here’s what we found” to “here’s what we agreed to”. This also produces the roadmap (/engagements/{id}/roadmap), with a Gantt view and a dependency-cycle check.

Lock & advance

When the readiness gate is met — critical gaps have complete chains, the design is committed — Lock & Advance moves the engagement to Phase 4.