The Naftiko Framework's Shipyard tutorial walks through eleven capability YAMLs — mock MCP at one end, a fully wired domain-driven aggregate at the other. Step 1 is what you run to prove the engine reads YAML. Step 11 is what you run to feel what the framework actually produces.

This post is about deploying step 11 with a single click.

What gets deployed

Three protocol adapters from one capability YAML:

Adapter Path Tools / resources

MCP POST /mcp list-ships , get-ship , list-legacy-vessels , create-voyage , get-ship-with-crew , get-voyage-manifest

REST /api/... Same domain as REST resources

SKILL /skill Skill groups for structured agent discovery

Backed by two consumed APIs:

Maritime Registry at mocks.naftiko.net/rest/naftiko-shipyard-maritime-registry-api/1.0.0-alpha2 — bearer auth

Legacy Dockyard at mocks.naftiko.net/rest/naftiko-shipyard-legacy-dockyard-api/1.0.0-alpha2 — API key auth

Both are public Naftiko mocks.…