- 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>
37 lines
2.3 KiB
Markdown
37 lines
2.3 KiB
Markdown
# 0009. The rate card is a run input, its JSON as text; Assessment has no upload step
|
|
|
|
| | |
|
|
|---|---|
|
|
| Status | Accepted |
|
|
| Date | 2026-11-05 |
|
|
| Decided by | Product owner, 2026-11-05: "Run input text" (the rate card is a run input, its JSON pasted into the run form or passed by the script) |
|
|
| Requirements changed | Supersedes [ADR 0003](0003.md) (the rate card as an uploaded JSON file). ALZ-ASM-01, 04 and 06 read the rate card from the run input `rate_card_document` |
|
|
|
|
## Context
|
|
|
|
- The first Assessment run, `exec_20d55cfe6fd7`, stopped at the intake ([ADR 0008](0008.md)): "0 Discovery packages
|
|
among the selected artifacts". The Discovery package was selected correctly.
|
|
- **The cause is how KAB passes run inputs.** Every run input reaches every step. The rate card was uploaded as the
|
|
run's `file`, so it also reached `p1`, the parse step wired to the Artifacts step's `files`. The parse activity
|
|
reads a `file` input before `files`, so `p1` parsed the rate card again and never saw the package. Its output was
|
|
the rate card's text.
|
|
- So while the rate card is uploaded as `file`, no Assessment agent can read Discovery. Discovery is unaffected: it
|
|
has one parse step, and its uploads are meant for it.
|
|
|
|
## Decision
|
|
|
|
- **No upload step.** The workflow starts with `a1` (Artifacts) and `p1` (parse), so `file` is never a run input.
|
|
- **The rate card is the run input `rate_card_document`:** its JSON as text, in the same format as before (Feature
|
|
README). The planner, the disposition agent and the critic take it under the same name, so no agent's behaviour
|
|
changes; only the descriptions say where it comes from (planner, disposition and critic 0.1.1).
|
|
- `scripts/kab_run_workflow.py` reads an input from a file with `--input rate_card_document=@<path>`.
|
|
|
|
## Consequences
|
|
|
|
- **The parse step only ever sees the Discovery package,** and the intake's check means something.
|
|
- **In the KAB run form the rate card is pasted,** not uploaded. It's small (a few kilobytes), so a text field is
|
|
enough. A large rate card would be better as a project artifact selected beside the package, which the intake would
|
|
then have to tell apart.
|
|
- **Any future step that parses an upload in a workflow that also parses artifacts hits the same rule.** Keep one
|
|
file-parsing source per workflow, or none.
|