The optional cloud work began with a boundary review rather than an endpoint.
The review defined cloud planning as a separate operation for creating or revising a plan when the user explicitly asks for more knowledge. It prohibited the same route from becoming daily conversation, automatic fallback, background profiling, cloud memory, or unreviewed plan mutation.
The next implementation turned those rules into contracts. Requests carry explicit consent and minimized planning summaries. Responses must represent drafts rather than accepted changes. Validation rejects missing consent, credential-like content, provider debug material, chat-shaped output, and instructions that imply automatic mutation.
The hosted client has an injectable transport and validates both sides of the exchange. The production runtime, however, installs an unavailable client. There is no endpoint, provider call, quota service, or consent interface in the executable product yet. The boundary is implemented; the service is not.
← Back to Mister M