Files
cp1-agents/individual-agents/ALZ-F02: Assessment & Disposition Workflow Agent/docs/adr/0003.md
Jonathan Boniface e22d037ab0 ALZ-F02 Assessment: individual agents, intake, rate card input, critic fixes
- Six declarative agents generated from the v1.1 stories (scaffold_from_stories.py, ADR 0001),
  and a 9-step workflow export (build_workflow.py).
- Code-only intake (ADR 0008) verifies the one Discovery package in code before any agent.
- The rate card is the run input rate_card_document; no upload step (ADR 0009).
- Critic 0.1.6 after live runs on crucible-kab-dev:
  - K-12 model independence checked at build time against each agent's deployed model
    (ADR 0010); the critic reports it from its two inputs;
  - receives in_cloud_estate for K-10; an unverified K-10 never fails the run alone;
  - K-08 allows the scoring note to list findings as advisory, as ALZ-ASM-04 must;
  - carries ALZ-ASM-03's and ALZ-ASM-04's rule sections, copied by the scaffold, so it can
    recalculate risk, confidence and TCO.
- The scaffold refuses to regenerate unless every story file is present.
- Case azure-crucible-kab-dev-assessment with an illustrative rate card.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

23 lines
1.2 KiB
Markdown

# 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.