A model-backed web feature is still a web feature: identity, work admission, streaming, rendering, side effects, and release all need owners. This track follows a maintenance-summary tool across those boundaries. A generated answer can assist a reviewer, but the server keeps control of access, cost, and actions. Work through the request gateway, stream, retrieval and tool boundary, and release gate in order; each lesson also links to its neighboring contracts.
Topics in this track
- Model Gateway Identity and Request Budgets — Keep provider credentials on the server and charge model work to an authorized user action.
- Generated Response Streaming and Cancel State — Frame partial output, bound buffers, and make interrupted answers visibly incomplete.
- Retrieved Content, Instructions, and Tool Permission — Keep retrieved text as evidence, not authority to call tools or change permissions.
- Model Output Evaluation and Release Control — Test factual and workflow outcomes before exposing a new model path to everyone.
Prerequisite paths
Backend and API Systems; Identity and Application Security; Streaming and Large Data Interfaces.
Practice path
Build Project: permission-bound maintenance summary and check decisions in Web Development: model-backed application decisions quiz.