Append a proposed plan revision

The machine-checked half of a plan (EDD section 6.1).

Every field here maps to a check on a real route. A field that does not belongs in the intent instead -- that split is what keeps "envelope" an enforceable word rather than a decorative one. Note there is no spend limit: owner-set limits are team- and project-scoped only (ENG-6083).

The write shape of intent: everything an approver reads except the quote.

estimated_cost_usd is deliberately absent. The field is derived at propose from FinetunePlanQuoteBasis and lives only on the response model, so a caller-supplied figure is a 422 rather than a stored value.

Pricing inputs the server quotes from. Assumptions, not constraints.

The stored estimated_cost_usd is derived from these fields via quote_cost_usd. They are not hashed: they are inputs to a value that already is.

The machine-checked half of a plan (EDD section 6.1).

Every field here maps to a check on a real route. A field that does not belongs in the intent instead -- that split is what keeps "envelope" an enforceable word rather than a decorative one. Note there is no spend limit: owner-set limits are team- and project-scoped only (ENG-6083).

The recorded, rendered, never-checked half of a plan (EDD section 6.1).

estimated_cost_usd is server-derived at propose (ENG-6414) and shown beside the work so a user can tell a rounding error from a serious bill. Spend is bounded by team and project limits (ENG-6083), not this row.

Pricing inputs the server quotes from. Assumptions, not constraints.

The stored estimated_cost_usd is derived from these fields via quote_cost_usd. They are not hashed: they are inputs to a value that already is.