Orcher ships cost governance with hard spend ceilings

Cost governance in Orcher now operates at the level of the individual directive.

Priced before dispatch

Every candidate provider call is priced before it is issued. Routing weighs the task requirement against the price of each acceptable option rather than defaulting to the largest available model.

Budget that binds

A directive carries a ceiling. Budget is decremented as the work proceeds, and execution halts at the ceiling. The enterprise learns about the limit at the limit, not in the following month's invoice.

Visible across providers

Because Orcher is provider-neutral, spend is reported in one place across every model vendor in use. Cost is attributable to the directive, the role, and the workflow that caused it.