Centralize Model Execution and Keep Answers With Their Feature

Context

Separate feature teams need a common accounting and provider boundary. The pinned query consumer uses it; the general Jazz AI prototype does not.

Decision

Require declared Platform model execution for routing, budgets, admission, evidence and charges, while each consuming feature constructs its question, validates the answer and owns domain effects.

Alternatives Considered

Independent provider requests in each feature: They fragment allowance, credentials, diagnostic evidence and failure handling.

Separate ledgers within each macroservice: They divide one customer allowance and require combined reporting across services.

Central execution with remotely supplied tool callbacks: Remote function boundaries require an additional callback protocol that the recorded direction does not provide.

Consequences

The provider import and host guard applies within the Platform repository. New features need declared operation routing and prices before using this runtime. Consumer validation remains responsible for domain correctness. Direct console replies remain an unresolved exception. Another macroservice needs the already recorded runtime-library and Platform-metering direction implemented.