Execution Lifecycle

1. Prepare text or structured_input
2. Submit execute
3. Platform admission checks auth, scopes, entitlement, quota
4. Platform returns 200 or 202
5. For async, consume stream_url, query_url, cancel_url
6. Persist returned sync output, usage_applications, optional exact_bridge, and async workflow references into local logs or events

If neutral protocol objects are being carried for richer context, embed them inside structured_input rather than treating them as the default top-level HTTP contract.

The public runtime stays at zhen-platform-core. Do not send follow-up workflow traffic directly to zhen-brain-core.