neossh Request Lifecycle Diagram

The Model Proposes, the Platform Decides

Reasoning stays in the client; the provider never touches infrastructure
Every read and every write is authorized, not only mutations
The catalog, not the conversation, defines what is possible

Approval Is Out of Band

Approval is absent from the model's tool catalog by design
A fresh SSO event is bound to the immutable plan digest
Typing a confirmation in chat cannot authorize execution

Verify, Then Report Uncertainty

A successful patch does not imply a healthy service
The worker watches rollout progress under a deadline
The receipt, not the conversation, is the record of outcome