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>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent 9e503885cc
commit e22d037ab0
153 changed files with 13004 additions and 0 deletions

View File

@@ -0,0 +1,22 @@
# 0007. ALZ-ASM-02 and ALZ-ASM-05 need all three discovery servers registered
| | |
|---|---|
| Status | Proposed |
| Date | 2026-11-02 |
| Decided by | Consequence of the Feature's MCP decision; recorded for deployment |
| Requirements changed | None (deployment prerequisite) |
## Context
A declared MCP server that isn't offered stops an agent's tools loading. ALZ-ASM-02 declares the three discovery servers. ALZ-ASM-05 declares the same three, including their `<provider>_search_well_architected` tools. (Until 2026-11-04 it also declared `cloud-knowledge`, which is now retired.)
## Decision
- **Both agents declare every server for every provider,** so one workflow works for a customer on any cloud. The cloud servers stay standalone and are never merged.
- **The three servers must be deployed and registered in the CP1 tenant** before either agent can start, even for an on-premises estate like Meridian.
## Consequences
- **This blocks the first workflow run.** The discovery servers aren't deployed, and customer credentials need the Vault Service.
- **For an on-premises sample run,** the servers only need to be registered and healthy, without customer credentials. Confirm that on the platform before relying on it.