Integrate one narrow capability and prove its behavior at the app boundary.
1. Vertical slice
Connect one screen, a ViewModel, an adapter and one inference operation. Avoid adding chat history, tools and retrieval together. A small slice makes failures attributable to one boundary.
2. Input and result validation
Apply input length limits before sending. Validate output fields after parsing and represent invalid output as a recoverable error. The model should never decide whether the user is authenticated.
3. Release readiness
Use a feature flag and an emergency off switch. Verify the fallback still works when the model service is unavailable. Record the model and prompt versions used in evaluation.
Worked scenario
A note summary feature first ships to internal testers. If inference fails, the original note remains editable and the UI explains how to retry.
Apply it
Connect the fake-backed screen to your selected supported integration. Re-run the same failure cases and record changed behavior.
Check your understanding
The feature remains usable when inference is disabled. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.