Check the safe-control boundary
Before the final explanation, review zone resolution, the intent gate, audit events, and the graph boundary in four questions.
Question for this chapter
Can you separate the boundaries that turn a natural-language request into safe chart control?
Why this matters now
You resolved a zone name to coordinates, ran an allowed command and a blocked question, and separated batch from runtime events. Before the final explanation, review the difference between convenient input, narrow execution authority, and audit coverage. This quiz has no passing score and does not lock the next chapter.
Core decision check
Select an answer to see the correct choice and its evidence immediately.
0/4 questions reviewed
Connect the evidence in one statement
Resolve the zone name to verified coordinates, allow only UI_CONTROL, record both allowed and blocked requests, and distinguish the graph's batch coverage from runtime history in the dataset.
Next decision
You have separated execution authority from audit coverage. In the final chapter, explain the complete safe-control flow from the operator request to structured output and allowed or blocked history.