Make guard and MCP runtimes explicit dependencies instead of Ward image passengers #1266

Closed
opened 2026-07-14 10:00:25 +00:00 by coilyco-ops · 1 comment
Owner

Decision

Go, from coilysiren/inbox#211.

Make agent-guard and agent-guard-mcp explicit runtime dependencies where Ward needs them, instead of letting the Ward image carry guard/MCP extras implicitly.

Scope

  • Inventory which guard, ops, and MCP binaries or assets are currently bundled into Ward images or assumed to be present in Ward runtime containers.
  • Define the explicit dependency contract for agent-guard and agent-guard-mcp after the rename work settles.
  • Update Ward image/build/deploy docs so the workflow kernel image is not the hidden delivery vehicle for unrelated guard/MCP runtime extras.
  • Identify any deploy or AOS follow-ups needed to wire the explicit dependencies into actual environments.

Non-goals

  • Do not execute the cli-guard -> agent-guard rename here; cli-guard#200 owns that.
  • Do not execute the ward-mcp -> agent-guard-mcp rename here; ward-mcp#19 owns that.
  • Do not remove runtime pieces until dependent flows have explicit replacements.

Parent: coilysiren/inbox#211.
Related: coilyco-flight-deck/cli-guard#200, coilyco-flight-deck/ward-mcp#19.

## Decision Go, from coilysiren/inbox#211. Make agent-guard and agent-guard-mcp explicit runtime dependencies where Ward needs them, instead of letting the Ward image carry guard/MCP extras implicitly. ## Scope - Inventory which guard, ops, and MCP binaries or assets are currently bundled into Ward images or assumed to be present in Ward runtime containers. - Define the explicit dependency contract for agent-guard and agent-guard-mcp after the rename work settles. - Update Ward image/build/deploy docs so the workflow kernel image is not the hidden delivery vehicle for unrelated guard/MCP runtime extras. - Identify any deploy or AOS follow-ups needed to wire the explicit dependencies into actual environments. ## Non-goals - Do not execute the cli-guard -> agent-guard rename here; cli-guard#200 owns that. - Do not execute the ward-mcp -> agent-guard-mcp rename here; ward-mcp#19 owns that. - Do not remove runtime pieces until dependent flows have explicit replacements. Parent: coilysiren/inbox#211. Related: coilyco-flight-deck/cli-guard#200, coilyco-flight-deck/ward-mcp#19.
Owner

I remember the idea here, but I'm not convinced ward needs the shape of the integration with either of those repos that was being imagined here

I remember the idea here, but I'm not convinced ward needs the shape of the integration with either of those repos that was being imagined here
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
2 participants
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward#1266
No description provided.