| Who controls client presentation and release? | Consultant-controlled branding and release workflow; pilot activation gated | Evaluate the selected service's presentation, licensing, and release controls | The practitioner chooses the tools and owns review, presentation, and release |
| How is State Plan routing represented? | 29 configured plans; runtime claims limited to exact receipts and disclosed gaps | Confirm the selected service's scope, jurisdiction model, and evidence boundaries | The practitioner defines and maintains the jurisdiction and source set |
| How is official-source evidence retained? | Every eligible published record keeps source, capture, and lifecycle dates distinct | Evaluate the available source, date, and audit fields for the chosen service | The practitioner captures, verifies, and preserves the official evidence |
| How are corrections tracked? | Authenticated correction and affected-recipient history; active after approved pilot launch | Evaluate the chosen service's correction and notification workflow | The practitioner maintains correction, supersession, and recipient records |
| What must be checked before starting? | The fully approved readiness envelope and every applicable launch gate, including reviewer and requested-jurisdiction coverage, are confirmed before any invitation or access | Assess scope, evidence, licensing, support, and fit for the intended workflow | Design the source, review, delivery, and correction controls |