Files
cp1-agents/individual-agents/ALZ-F01: Discovery Workflow Agent/docs/run-context-field-review.md
Jonathan Boniface 9e503885cc 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>
2026-11-05 22:13:25 +00:00

9.0 KiB

Run context: field-by-field review for ADR 0016

Date 2026-11-05
For The product owner, going through ADR 0016 (Proposed) field by field before value plan phase 2
Source The scope spec catalogue the ADR borrows (outcome-pattern/solution_architecture/.../skills/scoping/assets/catalogue.yaml), 51 fields
Status Recommendations only. Nothing is built from this until the decisions column is filled in

How to read it

  • Boundary (decided 2026-11-05): Discovery's output feeds only Assessment (F02). The solution architecture stream is separate, so nothing here is a hand-over to it, and F01 would keep its own copy of whatever fields it adopts, with its own catalogue. ADR 0016's points 1 and 5 (one file through to solution architecture; a shared catalogue) would be dropped.
  • Who settles it:
    • Evidence: Discovery can read the current value from the cloud or the CMDB, and records it with its provenance. The customer may still state a target; Discovery then reports current against stated.
    • Customer: only the customer can say it. Discovery reads it and uses it; it can be ask, decide or not_applicable.
    • Not Discovery: a design or delivery choice. It belongs to a later workflow, not to this file.
  • Used by: the step or consumer that would act on it today or in a planned phase.
  • Recommendation: Keep (adopt now), Later (worth having, no consumer yet), Drop (not Discovery's, or already covered).

Discovery's own sections stay as they are: workflow_inputs, generated, uploads, customer, plan, and context (scope, sources, owners, business_services, assets).

Fields

# Field What it is Who settles it Used by Recommendation Decision
1 metadata.customer_case The engagement's short reference Customer All Drop: workflow_inputs.engagement_id already is this
2 engagement.kind Workload, platform foundation or migration Customer Planner (what's essential), F02 Keep
3 intent.statement What the customer wants, in their words Customer Report (shown as data) Keep, as data only: never sent in a tool call, never passed to every step
4 intent.requirements Stated requirements with ids (REQ-01) Customer Well-Architected review (cite the REQ- behind a gap), report Keep
5 intent.exclusions What's out of scope Customer Planner Drop: context.scope.exclude already holds this for Discovery
6 intent.success_criteria How the customer judges success Customer — Later
7 estate.cloud_provider The provider Customer — Drop: workflow_inputs.provider is this
8 estate.mode Greenfield, brownfield expansion or migration Customer Planner, F02 Keep
9 estate.regions.primary The main region Evidence Planner, report Keep, settled from evidence; context.scope.regions stays the scan's filter
10 estate.regions.secondary A second region Evidence Report Keep, settled from evidence
11 estate.regions.resiliency_tier Single region, warm standby or active-active Evidence (current); customer (target) Well-Architected reliability Later
12 estate.data_residency Where data must stay Customer F02 (compliance), Well-Architected Keep
13 estate.existing_systems What exists today Evidence — Drop as a field: it is Discovery's whole output (inventory, applications)
14 workload.users.who Who uses it Customer — Later
15 workload.users.count How many users Customer — Later
16 workload.users.peak_concurrent Peak concurrent users Customer — Later
17 workload.availability.target Availability, as a percentage Customer Well-Architected reliability, F02 risk Keep, optional
18 workload.availability.hours Business hours, extended or always Customer F02 risk Later
19 workload.availability.recovery_time RTO Customer Well-Architected reliability, F02 Keep, optional
20 workload.availability.recovery_point RPO Customer Well-Architected reliability (backup checks), F02 Keep, optional
21 compliance.industry The customer's industry Customer Report Drop: customer.industry already holds it
22 compliance.frameworks Regulations and standards that apply Customer F02 compliance_scope (gap 11), Well-Architected policy sets Keep, essential: replaces customer.regulatory
23 compliance.data_classification How sensitive the data is Customer Classification step (stated against found), F02 Keep
24 compliance.encryption.type Provider- or customer-managed keys Evidence Well-Architected security Keep, settled from evidence
25 compliance.encryption.key_rotation_days Key rotation period Evidence (partly) Well-Architected security Later
26 compliance.audit_logging.retention_days Audit log retention Evidence (partly) Well-Architected operations Later
27 compliance.audit_logging.immutable_retention_policy Undeletable audit logs Evidence (partly) Well-Architected security Later
28 networking.exposure Internal only or internet-facing Evidence Network step, Well-Architected security Keep, settled from evidence
29 networking.topology The network topology Evidence Network step, report Keep, settled from evidence
30 networking.hybrid_connectivity.enabled Private links to on-premises or another cloud Evidence Network step, F02 Keep, settled from evidence
31 networking.hybrid_connectivity.type VPN, ExpressRoute, Interconnect Evidence Network step Keep, settled from evidence
32 networking.hybrid_connectivity.bandwidth_gbps Bandwidth Evidence (partly) — Later
33 networking.egress_control.model Direct, provider-managed or a central appliance Evidence Network step, Well-Architected security Keep, settled from evidence
34 networking.egress_control.appliance_vendor Which appliance Evidence (partly) — Later
35 networking.cidr_allocations Allocated IP ranges Evidence Network step (address overlap) Keep, settled from evidence
36 governance.identity_source_of_truth The identity provider Customer — Later
37 governance.pipeline_authentication How pipelines authenticate Not Discovery — Drop
38 governance.environment_tiers Which environments exist Evidence Inventory (environment), F02 Keep, settled from evidence (environment tags)
39 operations.operating_model Who runs it day to day Customer Owners (ADR 0021), F02 Later: owners now come from the CMDB and tags
40 operations.support_hours Supported hours Customer F02 risk Later
41 operations.monitoring Monitoring and alerting Evidence Well-Architected operations Keep, settled from evidence
42 operations.change_process How changes are approved Customer, or ITSM F02 change frequency Later, with an ITSM source
43 integrations Other systems it exchanges data with Evidence Dependency graph (external nodes) Drop as a field: the dependency graph holds it
44 delivery.target_start_date When work starts Not Discovery — Drop
45 delivery.window_weeks The deadline Not Discovery — Drop
46 delivery.commercial_model How the work is contracted Not Discovery — Drop
47 delivery.iac_tooling Infrastructure-as-code tool Not Discovery — Drop
48 delivery.ci_cd Pipeline tool Not Discovery — Drop
49 delivery.team_size Engineers building it Not Discovery — Drop
50 cost.monthly_budget Monthly running budget Customer F02 TCO (indicative) Later: F02 uses its rate card
51 constraints.products_required, products_forbidden Mandated or ruled-out products Not Discovery — Drop
Recommendation Fields
Keep 21 (10 the customer states, 11 settled from evidence)
Later 16
Drop 14 (6 already covered by Discovery's own sections or outputs, 8 delivery or design)

Also to decide

  1. Must every run have an intent, or is it optional, with the Well-Architected review weighting pillars equally when there's none? Recommended: optional.
  2. Where the completed values go: a completed copy of the context file, or only in the package (a new context part). Recommended: the package only, so there's one artifact for F02.
  3. ADR 0016's fate: rewrite it to the fields kept here, within F01 and F02, with no shared catalogue.