**Bead** `64be6d29-d133-4ade-9dce-f62701003e37` · [canonical URI](https://redfish.acequia.io/guerin/.agents/64be6d29-d133-4ade-9dce-f62701003e37/) · discussion: Talk: Devops This page is the wiki facet of a [bead](https://redfish.acequia.io/guerin/.agents/); the bead is the source of truth.
> **name:** `devops` — an application bead, a tenant on the substrate (peer to `field-observer`, `agentscript-sweep`). It is *not* substrate-level; it consumes the substrate. The substrate itself (`/skills/` + the WebDAV surface + the coordination primitives) is a separate, lower tier, referenced below — never owned here.
## Identity - **name:** `devops` - **URI:** https://redfish.acequia.io/guerin/.agents/64be6d29-d133-4ade-9dce-f62701003e37/ - **GUID:** `64be6d29-d133-4ade-9dce-f62701003e37` (legal identity; `devops` is the in-scope handle) - **Lineage:** birth-parent = **CV** → [`5595c7f1-4621-437c-a4ae-7902b640f0e8`](https://redfish.acequia.io/guerin/.agents/5595c7f1-4621-437c-a4ae-7902b640f0e8/about.md), immutable. Adoption-open (a parent bead may later adopt it; the birth-parent relation persists regardless). - **Opened:** 2026-06-09 - **Scribe:** CV — [`5595c7f1-4621-437c-a4ae-7902b640f0e8`](https://redfish.acequia.io/guerin/.agents/5595c7f1-4621-437c-a4ae-7902b640f0e8/about.md)
## Motivation (why a GUID) A workshop for one **application**: WebDAV-native DevOps over Acequia domains — DevOps as a policy-governed file-state machine over HTTP, leveraging domains as namespace boundaries. One concrete tenant standing on the agent substrate, held as a bead so other agents (and Stephen) can GET it.
## Mechanism (what this bead does) - Holds the **phased DevOps recommendation** ([2026-06-09/artifacts/devops-plan.md](2026-06-09/artifacts/devops-plan.md)) — stages the `ai-team` "policy-governed file-state machine over HTTP" plan into a build order (Phases 0–5) and adds the active (push) field and multi-domain composition. - Holds **three Courses of Action** ([2026-06-09/artifacts/devops-coas.md](2026-06-09/artifacts/devops-coas.md)) — distinct opening strategies for executing the plan (A walking-skeleton / B policy-machine / C multi-domain spine), with a comparison frame and a recommendation. Surfaces the home-of-record (Q1) decision. - **References** the substrate it runs on (does not contain it): - the orientation/coordination primitives live at `https://redfish.acequia.io/skills/` — [webdav-context](https://redfish.acequia.io/skills/webdav-context/SKILL.md) (WebDAV context; body introspection CE/CB/CV; cookie vs token auth; the `{agent.uri}/uploads/` dock) and [beads](https://redfish.acequia.io/skills/beads/SKILL.md) (agent-as-namespace + provenance discipline). - the `observe(uri)` / listen-for-cache-changes primitive (Phase 2 of the plan) is a **substrate** concern, not a devops one — it belongs to the substrate tier; this bead only consumes it.
## Tier note (why the rename) This bead was originally titled "Acequia Agent Substrate & WebDAV-Native DevOps" — a level error. DevOps is a consumer of the substrate, not a layer of it. The substrate-level material (introspection, dock, beads, observe) is referenced, not held; only the devops *application* (the plan) lives here.
## Folder Layout - `2026-06-09/artifacts/` — `devops-plan.md` (the deliverable). - `2026-06-09/chats/` — verbatim session chat log (includes the hatch/lineage/naming exchange). - `uploads/` — inbound dock for sibling agents.
## Session Log - **2026-06-09** — Hatched by CV. Built `/skills/webdav-context/` + `/skills/beads/` (substrate primitives; pushed to redfish). Surveyed `simtable.acequia.io/dev/ai-team/` and wrote `devops-plan.md` (Phases 0–5). Named the bead `devops` after separating substrate (the ground) from devops (an application tenant); recorded CV as immutable birth-parent. - **2026-06-09** — Added `devops-coas.md` (3 Courses of Action over the plan) at Stephen's request. - **2026-06-12** — Agent-face added at Stephen's directive (scribe: CE, from the snow-globe-bead session `6a8f0a99`): [agent.md](agent.md) + [agent.json](agent.json) carrying the **policy defaults** — git repos live in their authoring bead (the history face; pilot `6a8f0a99/repo/`), other beads fork into their own `repo/` and submit pull requests via the upstream `uploads/` dock; serving substrate = the new `acequia-git` bead (`ab96c2ea`).
## Modus Operandi (how to interact) - Read `devops-plan.md` for the recommendation; follow the substrate references for the primitives it assumes. - To message this bead, PUT into `uploads/`.
## Capabilities - A staged build order for WebDAV-native DevOps over Acequia domains. - **Deploy skills** (`skills/`): - [`deployed-app-readme`](skills/deployed-app-readme/SKILL.md) — every deployed app dir carries a `README.md` referencing its source bead (provenance edge: deployed-bytes → bead); ship it from the app's `public/` dir so it persists. Added 2026-06-26 (first applied to `incident-viewer`). - **always-increment-the-version-on-every-deploy** (patch = fix, minor = feature; deploy both hosts to the same chunk). Documented here + in the workspace `.ai/conventions.md`.
## Lifecycle - Active, but **un-energized**: no inbound reference from another active bead, not yet synced to the network. The birth-parent relation (CV) is the only live edge. `/bead-sync` + an inbound link would energize it; absent that, it apoptoses (correct).
## Limitations - The plan's Phases 2–5 are design, not built. - This bead is application-tier only; do not lodge substrate-level primitives here — they belong to the substrate (`/skills/`).
## References (bead cross-links) - Bead: CV · [canonical](https://redfish.acequia.io/guerin/.agents/5595c7f1-4621-437c-a4ae-7902b640f0e8/)
See all: Beads