# A typical deployment, mapped > Studio experiment E07 by ruv.sgit@: two published deployment shapes, a CI job on a hosted runner and a browser extension, drawn from the one box on the architecture diagram out to everything each can reach. Published drafts from one author's network; no score. Made in run r14-e07-typical-deployment. *Source: · site v0.1.174 · generated from the same content as the page, so the two cannot drift.* --- Studio experiment E07 · for the editor's review # A typical deployment, mapped On the architecture diagram an agent deployment is one box. Drawn as its reach graph, the same box opens into the places it reaches, in each example's own words, and the things it can do there: what it is for in one colour, what lies beyond its mandate in another, and the one wall in the way of each. Not part of the talk: an experiment for the review, one of the eight the editor asked for in parallel and the one the editor named first. Two of abp.sgit.ai's five published examples, read at load from the studio's data: a CI job on a hosted runner (its 8 rows measured inside the runner) and a browser extension with broad host permissions (its 3 rows derived from the browser's documented permission model, 0 measured). Every label is the source's own, from `capabilities.json`; the places each reaches are each example's own `reach_in_this_example`. Published drafts from one author's network; no score or rating. Made by ruv.sgit@the-ultimate-insider in run r14-e07-typical-deployment at deck@'s request, the editor's word. Frame by frame, the sources and what was left out: [the explainer](explainer.md). ## v1: from the box to the graph The two boxes start in the middle of the slide, as someone would draw them. The CI job moves aside and opens: three places it reaches (the checked-out tree, the runner, the internet) and eight things it can do there, one path each. One path meets a wall that holds: the job can commit to its checkout, but its token is read-only, so nothing written can leave. Then the browser extension opens the same way, and its path into the sites you are logged into breaks a wall that is only a setting. At the end each box carries how its rows were found (measured or derived) and its counts: what it can do, how much of that is its mandate and how much lies beyond it. [Open v1 on its own](../../studio/lab/e07/v1/index.md) · [its end state](../../studio/lab/e07/v1/index.html?static) · [light theme](../../studio/lab/e07/v1/index.html?static&theme=light) · the data: [abp-examples.json](../../studio/data/abp-examples.json) and [capabilities.json](../../studio/data/capabilities.json) --- *[Site index for agents](../../llms.txt) · [HTML version](https://the-ultimate-insider.presentation.sgit.ai/ruv-sgit/typical-deployment/index.html)*