KCAE.ENCOUNTER:4.1 - Choose an occasion and obtain observation authority

Start from work whose receiving result can matter, not from the available telemetry. Possible occasions include a handover, a changed configuration, a failed test, an unusual manual correction or a scheduled review already attended by a responsible person. Also inspect successful work: repeated compensation can make an inadequate input appear satisfactory. A failure-only trigger cannot expose that class.

Name who authorizes the observation, which events and fields may be used, for what purpose, for how long, and which recipient can receive the result. Obtain the permission through the actual owner. If it is absent, propose an attainable manual occasion or ask for the needed authorization; do not infer consent from installing a skill. State the stop on permission withdrawal.

The occasion must exist in the runtime or practice. A document describing a background observer is not that observer. A callable MCP tool exposes operations when invoked; it does not by itself watch a work stream. A skill can teach a response; it cannot alone schedule its own invocation. Choose an existing human participant, event subscriber, timer, application hook or explicit invocation that actually supplies the opening.