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>
15 lines
1.4 KiB
Markdown
15 lines
1.4 KiB
Markdown
# CP1 - Assessment Report Agent
|
|
|
|
Writes the Assessment report (ADR 0015). Step `s7` of the workflow "CP1 - Agentic Landing Zone - Assessment", after
|
|
the critic. It carries the `disposition_signoff` review point, so the Engagement Lead signs off from the report.
|
|
|
|
| Stage | Who | What |
|
|
|---|---|---|
|
|
| `pre_process` | code (`app/facts.py`, `app/discovery.py`) | Works out the facts from every step's output and from the Discovery package (what each application is: its assets, owner, data stores and dependencies): the register, gaps and scorecard (the package's own code), each disposition's rule trace and confidence workings, the critic's checks, the top security findings, and the lineage. The model receives the facts, not the raw step outputs |
|
|
| model | `gpt-5.6-sol` | Writes `report_markdown` from the facts: summary, what signing off means, dispositions, confidence, risk, cost, security (advisory), what would raise confidence, assurance and lineage (`prompt.md`) |
|
|
| `post_process` | code (`app/markdown.py`) | Sets the verdict and ids from the facts and renders `report_html` (marked as a draft, shown at the review point) and `final_html` (for the page step, `s9`, after approval). The model's text is HTML-escaped before any markup is added |
|
|
|
|
After the review point, the package (`s8`) holds the report's Markdown as its `report` part.
|
|
|
|
Tests: `python3 -m pytest tests/` (no runtime, no model), on run `exec_49e355141382`'s step outputs.
|