{"artifact":{"apiPath":"/api/reports/agent-approvals-and-human-leashes-2026/charts","byteLength":1653,"description":"Structured chart payload backing the inline report visuals and machine-readable consumers.","format":"charts","label":"Chart data artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"6d04befd682d34358353c018838412815e37ed9acd96fe68c1dfd01809b095d3","status":"live"},"document":{"charts":[{"caption":"Create and publish should stay human-presence heavy. Steady-state runtime should be leash heavy. Resume and renew are blended checkpoints.","chartType":"bar","points":[{"label":"Create","note":"Before a workflow exists, the key question is explicit human intent around budget, capability, and private scope.","values":[4,0,0]},{"label":"Run","note":"During normal execution, the system should lean on runtime leash and policy checks instead of asking for a fresh click every safe step.","values":[1,4,0]},{"label":"Resume","note":"Recovery needs both: a valid delegated envelope and, when the stop reason was approval or ambiguity, a fresh human decision.","values":[3,2,0]},{"label":"Renew","note":"Renewal is the point where continuing authority is reconsidered, so human approval and leash posture both matter.","values":[3,3,0]},{"label":"Publish","note":"Outward-facing release should rely on diff-aware review and fresh user presence, not on the same delegation used during execution.","values":[2,0,4]}],"series":["approval or review","active leash","fresh step-up"],"title":"Which control surface should dominate each workflow stage","unit":"relative control weight"}],"generatedAt":"2026-03-23T00:00:00.000Z","slug":"agent-approvals-and-human-leashes-2026"},"generatedAt":"2026-05-04T00:17:51.542Z","kind":"deep_report_charts","operatorAccess":null,"payer":null}