F02: Assessment report and package (ADR 0014, 0015); register agents in KAB
Some checks failed
check agents / check (push) Failing after 14s
Some checks failed
check agents / check (push) Failing after 14s
- Report (cp1-assessment-report-agent 0.2.0, step s7): a model writes the Assessment report from facts worked out in code (register, gaps, scorecard, rule traces, checks, and what each application is from the Discovery package); code sets the verdict and renders the pages. The disposition_signoff review point moves from the critic to the report. - Package (cp1-assessment-package-agent 0.1.1, step s8): after sign-off, every step's output in one package, with a register, a gaps register, the sign-off record, lineage and a sha256 per part, in code. Page step s9. - scripts/kab_register_agents.py: registers deployed agents in KAB's agent catalog (an in-place workflow update doesn't). - Runs exec_1b1257380df7 (014) and exec_374d5d577077 (015) completed on crucible-kab-dev: critic pass, report figures all in its facts, package complete with every digest recomputing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -3,7 +3,8 @@
|
||||
Six declarative KAB agents, one per ALZ-ASM story, chained by one KAB workflow, behind a code-only intake step that
|
||||
checks the Discovery package first (ADR 0008). They take an approved Discovery run's package and a rate card. For every application they produce a readiness profile, a migration risk score,
|
||||
advisory security findings (in-cloud estates only), a 7R disposition with an indicative TCO, and an independent
|
||||
critic's verdict. The Engagement Lead approves the verdict as `disposition_signoff`.
|
||||
critic's verdict, then a report the Engagement Lead signs off from as `disposition_signoff`, and one package for the
|
||||
later Features.
|
||||
|
||||
Requirements: ADO Feature 3214442, stories 3214459–3214464. The sub-agent pattern for this Feature isn't built yet,
|
||||
and the two are kept separate.
|
||||
@@ -22,10 +23,17 @@ and the two are kept separate.
|
||||
| `s3` | [Migration Risk Scorer](cp1-migration-risk-scorer-agent/) (ALZ-ASM-03) | `p1`, `s1` |
|
||||
| `s4` | [Security Posture Assessment](cp1-security-posture-assessment-agent/) (ALZ-ASM-05): not applicable on-premises | `p1`, `s1` |
|
||||
| `s5` | [7R Disposition & TCO](cp1-disposition-tco-agent/) (ALZ-ASM-04) | `p1`, the run's `rate_card_document`, `s1`, `s2`, `s3`, `s4` |
|
||||
| `s6` | [Assessment Critic & Sign-off Router](cp1-assessment-critic-agent/) (ALZ-ASM-06): **approval step** | All of the above |
|
||||
| `s6` | [Assessment Critic & Sign-off Router](cp1-assessment-critic-agent/) (ALZ-ASM-06) | All of the above |
|
||||
| `s7` | [Assessment Report](cp1-assessment-report-agent/) (ADR 0015): a model writes the report from facts worked out in code; **approval step** (`disposition_signoff`) | `s0` to `s6` |
|
||||
| `s8` | [Assessment Package](cp1-assessment-package-agent/) (ADR 0014): after the approval, one package for Strategy and the later Features, in code: every step's output, a register per application, a gaps register, the report and the sign-off record | `s0` to `s7`, the run's inputs |
|
||||
| `s9` | Format Assessment report for UI: the approved report as a page | `s7` |
|
||||
|
||||
`s2`, `s3` and `s4` run in parallel.
|
||||
|
||||
The Engagement Lead signs off from the Assessment report (`s7`, ADR 0015). The run's deliverables are the package
|
||||
(`s8`, ADR 0014) and the report's page (`s9`). Both exist only for a run continued at `disposition_signoff`, and
|
||||
continuing signs off the sign-off queue as it stands.
|
||||
|
||||
## Starting a run
|
||||
|
||||
1. **Choose a Discovery run** whose critic verdict is `pass` and which was approved. Note its execution id and the
|
||||
|
||||
Reference in New Issue
Block a user