# 0003. The rate card is an uploaded JSON file | | | |---|---| | Status | Superseded by [0009](0009.md) | | Date | 2026-11-02 | | Decided by | Built as a default; the source (rate card uploaded with the run) was decided by the product owner on 2026-11-02 | | Requirements changed | ASM-01 CAP-01 and ASM-04 CAP-03 / CAP-04 (form of the rate card) | ## Context The Feature decided that target rates and licensing terms come from a rate card uploaded with the run, but not its format. ## Decision - **Upload:** the rate card comes through the run form's `file` field on `u1`, and the planner, the disposition agent and the critic take `u1.parsed_content` as `rate_card_document`. - **Format:** JSON with `rate_card_id`, `currency` and `items`. Each item has `rate_id`, `category`, `description`, `annual_rate`, `equivalent_for` (services, products or asset classes) and `licence_terms`. A sample is in `workflows/cases/meridian-assessment/rate-card.json`. ## Consequences - **A missing rate stops nothing,** but it's named in `missing_inputs` and the TCO stays partial. - **Another format (a spreadsheet, say) arrives as parsed text** and is harder for the agents to read reliably. Keep to JSON until a template exists.