coilysiren/website

Watch

Publish a Ward MCP case study for guarded MCP delivery #86

New issue

Closed

opened 2026-08-03 00:51:51 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-03 00:51:51 +00:00

Collaborator

Parent

Private Inbox epic

Actor

Design role.

Outcome

Publish a Ward MCP case study that shows how guarded policies become usable MCP services without confusing tool discovery with authority.

Context

Ward MCP is the integration layer in this three-part portfolio story. Its public positioning is an MCP runtime that turns cli-guard policy files into guarded Streamable HTTP services and container images.

The page should make the security and platform boundary legible: a client can discover a tool, but the server-side policy still determines what the tool may do.

What to build

Lead with the gap between exposing an MCP tool and granting safe authority.
Show the verified path from policy source through the Ward MCP runtime to a bounded Streamable HTTP tool surface.
Explain where validation, credentials, and enforcement live using current repository evidence.
Show one representative guarded request and the user-visible result.
Name one hard tradeoff, such as stable developer ergonomics versus a deliberately narrow permission surface.
Distinguish Ward MCP from Ward's workflow layer and agent-compose's context layer.
Connect the page back to the broader compose, execute, and expose system story.

Blocked by

Blocked by the hiring-page refresh so the case study can replace its temporary repository link cleanly.

Shared acceptance boundary

The page uses current canonical repository evidence rather than remembered architecture.
The page names the problem, architecture, hard design judgment, evidence, and current limit.
The page links to the canonical Forgejo source and the hiring page links back to this case study.
Metadata and social preview are intentional, and the page is legible on desktop and mobile.
No private project, opaque identifier, invented metric, or unsupported outcome appears.
Repository validation passes and the change lands through the repository's normal workflow.

Non-goals

Do not duplicate the repository README.
Do not write a changelog or exhaustive feature inventory.
Do not claim that telemetry alone creates trust.
Do not redesign unrelated site surfaces.

## Parent [Private Inbox epic](https://forgejo.coilysiren.me/coilysiren/inbox/issues/319) ## Actor Design role. ## Outcome Publish a Ward MCP case study that shows how guarded policies become usable MCP services without confusing tool discovery with authority. ## Context Ward MCP is the integration layer in this three-part portfolio story. Its public positioning is an MCP runtime that turns cli-guard policy files into guarded Streamable HTTP services and container images. The page should make the security and platform boundary legible: a client can discover a tool, but the server-side policy still determines what the tool may do. ## What to build * Lead with the gap between exposing an MCP tool and granting safe authority. * Show the verified path from policy source through the Ward MCP runtime to a bounded Streamable HTTP tool surface. * Explain where validation, credentials, and enforcement live using current repository evidence. * Show one representative guarded request and the user-visible result. * Name one hard tradeoff, such as stable developer ergonomics versus a deliberately narrow permission surface. * Distinguish Ward MCP from Ward's workflow layer and agent-compose's context layer. * Connect the page back to the broader compose, execute, and expose system story. ## Blocked by Blocked by [the hiring-page refresh](https://forgejo.coilysiren.me/coilysiren/website/issues/83) so the case study can replace its temporary repository link cleanly. ## Shared acceptance boundary * [ ] The page uses current canonical repository evidence rather than remembered architecture. * [ ] The page names the problem, architecture, hard design judgment, evidence, and current limit. * [ ] The page links to the canonical Forgejo source and the hiring page links back to this case study. * [ ] Metadata and social preview are intentional, and the page is legible on desktop and mobile. * [ ] No private project, opaque identifier, invented metric, or unsupported outcome appears. * [ ] Repository validation passes and the change lands through the repository's normal workflow. ## Non-goals * Do not duplicate the repository README. * Do not write a changelog or exhaustive feature inventory. * Do not claim that telemetry alone creates trust. * Do not redesign unrelated site surfaces.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-03 00:53:15 +00:00

coilyco-ops commented

2026-08-03 02:05:16 +00:00

Author

Collaborator

Landed in ffc01ca433. /work/ward-mcp/ now shows the policy-to-runtime-to-bounded-tool path, a representative guarded request, the deny-by-absence judgment, shipped interface evidence, current inbound-auth boundary, and its place in the larger system.

Landed in https://forgejo.coilysiren.me/coilysiren/website/commit/ffc01ca433ca54f4af1f574465a0ccd652b2d0fd. `/work/ward-mcp/` now shows the policy-to-runtime-to-bounded-tool path, a representative guarded request, the deny-by-absence judgment, shipped interface evidence, current inbound-auth boundary, and its place in the larger system.

coilyco-ops closed this issue

2026-08-03 02:05:18 +00:00

No milestone

No project

No assignees

1 participant

Notifications

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

coilysiren/website#86

No description provided.

Rows
Columns