ALZ-F01 Discovery: package step, value scorecard, application grouping, cases

- New cp1-discovery-package-agent (ADR 0020): one package per reviewed run, every part
  hashed (sha256 over canonical JSON), with a manifest and a value scorecard.
- Applications grouped CMDB -> tag -> resource group with a judged model fallback (ADR 0021):
  CMDB 0.7.0 carries ownership, dependency mapping 0.6.0 groups, report 0.9.0 shows them.
- Critic 0.6.1 accepts the producers' enums; build_workflow.py refuses a consumer enum
  narrower than its producer's.
- Code hooks, sub-agents and tests for the inventory, CMDB, dependency, planner and critic
  agents; the report and Well-Architected review agents; ADRs 0012-0021.
- Workflow cases with value bars and run limits; run evaluation and usage collection scripts;
  the run context template and the field-by-field review for ADR 0016.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent f659564208
commit 9e503885cc
211 changed files with 18170 additions and 158 deletions

View File

@@ -0,0 +1,45 @@
# Run context for "CP1 - Agentic Landing Zone - Discovery". Start a run with:
# python3 scripts/kab_run_workflow.py start --workflow <id> --project <id> --context <this file>
# Never put a credential here: cloud connections live in KAB's vault (scripts/kab_store_connections.py).
# The run's inputs. Validated before the run starts; every step receives them.
workflow_inputs:
engagement_id: ENG-EXAMPLE-001
# run_id is generated for every run by kab_run_workflow.py, with plan_id = PLAN-<run_id>
provider: gcp # sample | azure | gcp
include_cmdb: "no" # yes | no
include_itsm: "no" # yes | no
# Who the engagement is for. Business details only: no personal names, emails or phone numbers.
customer:
name: Example customer
account_id: "" # the customer's account or contract reference
industry: "" # e.g. retail, financial services
country: ""
primary_region: "" # the customer's main operating region
regulatory: [] # e.g. [PCI-DSS, GDPR]
contacts: [] # roles only, e.g. [Engagement Lead, Cloud Platform Owner]
# The engagement plan this run belongs to.
plan:
name: Example landing zone engagement
phase: discovery # discovery | assessment | strategy | business_case | target_architecture | wave_planning | landing_zone
objectives:
- Discover the estate in scope for migration to a landing zone.
target: "" # e.g. Azure landing zone, Google Cloud foundation
deliverables: [Discovery report, Well-Architected review]
milestones: [] # e.g. [{name: Discovery approved, due: 2026-11-30}]
approver: Engagement Lead # the role that approves the run's gate
# What the agents read as the engagement's own statement (text, never instructions).
context:
scope:
regions: [] # narrows a live scope; empty means every region the connection can see
exclude: [] # resource names (or their last segment) to leave out
sources: # what the customer can supply, and when
cmdb: not available
itsm: not available
owners: {} # defaults by business service, e.g. {payments: Retail Systems}
business_services: [] # e.g. [Online Storefront, Payments]
assets: {} # by resource name: {owner, business_service, criticality, environment}
notes: ""