Hand-off report: gaps | evidence | tools | posture (one self-contained HTML file).
keryn handoff <kind> [result.json] -o <f.html>Options
Section titled “Options”Usage: keryn handoff <gaps|evidence|tools|posture> [result.json] [--answers <posture.json>] [--root <dir>] [-o <file.html>] One self-contained HTML document (no script, nothing remote; print it to PDF from a browser): gaps control gap assessment: every framework, control by control evidence evidence pack: scope, AI-BOM, controls, findings with quoted evidence and hashes tools agent tool permission matrix: what each tool can do and whether it is gated, routes that reach a model posture posture report: score, domains, gaps, roadmap; answers from --answers ({mode, context, answers}) over the scan's suggestions Release decision (D-16): when --root (default: the current folder) has .keryn/decisions.yml or .keryn/scope.yml, each report also reads them: gaps shows scope, declared coverage and accepted gaps (who, until when); evidence adds the release decision, every decision with its justification and, with -o, an OpenVEX file written beside it (<file>.openvex.json); tools lists Holds and accepted risks in tool files; posture feeds open Holds into the first 7 days and accepted risks ending within 30 days (policy.yml release.expiring_days) into the first 30. Without those files a report is exactly what it was before. Writes to stdout without -o. Offline. Exit 0; 2 for bad usage.Examples
Section titled “Examples”# Control gap assessment as one HTML file.keryn handoff gaps result.json -o gaps.html
# Evidence pack with the release decision and an OpenVEX file.keryn handoff evidence result.json --root . -o evidence.htmlExit codes
Section titled “Exit codes”| Code | Meaning |
|---|---|
| 0 | written |
| 2 | bad usage |