1import{j as e}from"./main-CtuSTsQT.js";let d={title:"Generated Reports",description:"Curated, redacted examples of the reports autocontext produces while evaluating and improving agent runs."},c=` 2 3Generated reports show the evidence autocontext leaves behind after a run: what the agent attempted, how evaluation changed across generations, which findings survived, and what the next run inherits. 4 5These examples are generated from reviewed, synthetic fixtures. They do not contain customer runs, credentials, private prompts, or live production data. 6 7<Cards> 8 <Card href="/docs/reports/example-run" title="Example Run Report" description="Inspect a representative run summary rendered directly from autocontext's generated HTML artifact." /> 9</Cards> 10 11## How to Use These Reports [#how-to-use-these-reports] 12 13Read a generated report alongside [runs, traces, and artifacts](/docs/concepts/runs-traces-artifacts) to understand where each piece of evidence comes from. For the machine-readable report contracts, see [run report contracts](/docs/reference/contracts/run-reports). 14 15The website adapts trusted report HTML to the documentation theme. Scripted behavior is intentionally removed, so published examples remain static and reviewable. 16`,h={contents:[{heading:void 0,content:"Generated reports show the evidence autocontext leaves behind after a run: what the agent attempted, how evaluation changed across generations, which findings survived, and what the next run inherits."},{heading:void 0,content:"These examples are generated from reviewed, synthetic fixtures. They do not contain customer runs, credentials, private prompts, or live production data."},{heading:void 0,content:`<Card href="/docs/reports/example-run" title="Example Run Report" description="Inspect a representative run summary rendered directly from autocontext's generated HTML artifact." />`},{heading:"how-to-use-these-reports",content:"Read a generated report alongside runs, traces, and artifacts to understand where each piece of evidence comes from. For the machine-readable report contracts, see run report contracts."},{heading:"how-to-use-these-reports",content:"The website adapts trusted report HTML to the documentation theme. Scripted behavior is intentionally removed, so published examples remain static and reviewable."}],headings:[{id:"how-to-use-these-reports",content:"How to Use These Reports"}]},p=[{depth:2,url:"#how-to-use-these-reports",title:e.jsx(e.Fragment,{children:"How to Use These Reports"})}];function o(r){const t={a:"a",h2:"h2",p:"p",...r.components},{Card:n,Cards:a}=t;return n||s("Card"),a||s("Cards"),e.jsxs(e.Fragment,{children:[e.jsx(t.p,{children:"Generated reports show the evidence autocontext leaves behind after a run: what the agent attempted, how evaluation changed across generations, which findings survived, and what the next run inherits."}),` 17`,e.jsx(t.p,{children:"These examples are generated from reviewed, synthetic fixtures. They do not contain customer runs, credentials, private prompts, or live production data."}),` 18`,e.jsx(a,{children:e.jsx(n,{href:"/docs/reports/example-run",title:"Example Run Report",description:"Inspect a representative run summary rendered directly from autocontext's generated HTML artifact."})}),` 19`,e.jsx(t.h2,{id:"how-to-use-these-reports",children:"How to Use These Reports"}),` 20`,e.jsxs(t.p,{children:["Read a generated report alongside ",e.jsx(t.a,{href:"/docs/concepts/runs-traces-artifacts",children:"runs, traces, and artifacts"})," to understand where each piece of evidence comes from. For the machine-readable report contracts, see ",e.jsx(t.a,{href:"/docs/reference/contracts/run-reports",children:"run report contracts"}),"."]}),` 21`,e.jsx(t.p,{children:"The website adapts trusted report HTML to the documentation theme. Scripted behavior is intentionally removed, so published examples remain static and reviewable."})]})}function u(r={}){const{wrapper:t}=r.components||{};return t?e.jsx(t,{...r,children:e.jsx(o,{...r})}):o(r)}function s(r,t){throw new Error("Expected component `"+r+"` to be defined: you likely forgot to import, pass, or provide it.")}export{c as _markdown,u as default,d as frontmatter,h as structuredData,p as toc};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.